Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e48870ae3473b2a0c8fc23a73a2e6bfae91edbcb194435f5ea198aadc27dfa0

Tx prefix hash: 790ed876c6b33f169a9794d13878e05f56ef687343bbc95d956fb8563ebc183f
Tx public key: 6469fb2137e1ad467e1d04e3817ed27bba793061850171b1f2b1cea1928f6f3b
Timestamp: 1714061462 Timestamp [UCT]: 2024-04-25 16:11:02 Age [y:d:h:m:s]: 00:255:21:43:38
Block: 1008324 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183178 RingCT/type: yes/0
Extra: 016469fb2137e1ad467e1d04e3817ed27bba793061850171b1f2b1cea1928f6f3b0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75cc3a2972cb4b09975e46f69615fd7930be298ecf034a4bcb46aac76c0ea9e2 0.600000000000 1469792 of 15

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": 1008334, "vin": [ { "gen": { "height": 1008324 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75cc3a2972cb4b09975e46f69615fd7930be298ecf034a4bcb46aac76c0ea9e2" } } ], "extra": [ 1, 100, 105, 251, 33, 55, 225, 173, 70, 126, 29, 4, 227, 129, 126, 210, 123, 186, 121, 48, 97, 133, 1, 113, 177, 242, 177, 206, 161, 146, 143, 111, 59, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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