Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fea3146dd38c846d34b2293fcadff111dff0fb77c72831d363c442c973cdda44

Tx prefix hash: d87a4bd60154b9cc1646a874e99756cf5d75a47fccc2611a4ae212adf6e9a0eb
Tx public key: aaa7e7102af8c269bb0229eee5e02a4898b8430558e872b91946dfb9da8e7096
Timestamp: 1706635222 Timestamp [UCT]: 2024-01-30 17:20:22 Age [y:d:h:m:s]: 01:066:05:41:48
Block: 946738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308413 RingCT/type: yes/0
Extra: 01aaa7e7102af8c269bb0229eee5e02a4898b8430558e872b91946dfb9da8e70960211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 358a8c3d926382543af1c68ae4b91b1130d4b6426a2cccc73d1011b30eff681e 0.600000000000 1405078 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": 946748, "vin": [ { "gen": { "height": 946738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "358a8c3d926382543af1c68ae4b91b1130d4b6426a2cccc73d1011b30eff681e" } } ], "extra": [ 1, 170, 167, 231, 16, 42, 248, 194, 105, 187, 2, 41, 238, 229, 224, 42, 72, 152, 184, 67, 5, 88, 232, 114, 185, 25, 70, 223, 185, 218, 142, 112, 150, 2, 17, 0, 0, 0, 2, 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