Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 46fb31b06e3d88a74cb575e7e5f173030d8a925089db3c0120d0480539be74f7

Tx prefix hash: 166f99ff18bde7009c59e809681f968d02a9ef9520fc8f0068e45fa6d3d1d99e
Tx public key: d862ad6ad9a5faa53c0cdd592f4e868d91de142424179cca8d91aa7bec66829f
Timestamp: 1694313375 Timestamp [UCT]: 2023-09-10 02:36:15 Age [y:d:h:m:s]: 01:121:10:23:16
Block: 844785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348109 RingCT/type: yes/0
Extra: 01d862ad6ad9a5faa53c0cdd592f4e868d91de142424179cca8d91aa7bec66829f0211000000064b8f5122000000000000000000

1 output(s) for total of 0.974712807000 dcy

stealth address amount amount idx
00: 0ee8e366623de68f8f409ac32cb044a71fa18b3e0f01b5078ae966e9b2ee2a50 0.974712807000 1298115 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 844795, "vin": [ { "gen": { "height": 844785 } } ], "vout": [ { "amount": 974712807, "target": { "key": "0ee8e366623de68f8f409ac32cb044a71fa18b3e0f01b5078ae966e9b2ee2a50" } } ], "extra": [ 1, 216, 98, 173, 106, 217, 165, 250, 165, 60, 12, 221, 89, 47, 78, 134, 141, 145, 222, 20, 36, 36, 23, 156, 202, 141, 145, 170, 123, 236, 102, 130, 159, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8