Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a454a175e7e29e5f9e313fc44f300cc8f0f343e676c3a5be0586bd90fb671c52

Tx prefix hash: 5ff5e2a957079b354dc9c76d31e2db3d7178a18fea459d41610ef74931e1240c
Tx public key: 014f254ee0fe4c561307497c2b5fe7a2c9b92f93b27e9812aec9302404a4b713
Timestamp: 1683646918 Timestamp [UCT]: 2023-05-09 15:41:58 Age [y:d:h:m:s]: 01:257:09:13:40
Block: 756433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445361 RingCT/type: yes/0
Extra: 01014f254ee0fe4c561307497c2b5fe7a2c9b92f93b27e9812aec9302404a4b713021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.912597811000 dcy

stealth address amount amount idx
00: 05137ff6d2fecf09647372c98c08dc39c4f073ed551c3d13e19208aa6510e90d 1.912597811000 1204810 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": 756443, "vin": [ { "gen": { "height": 756433 } } ], "vout": [ { "amount": 1912597811, "target": { "key": "05137ff6d2fecf09647372c98c08dc39c4f073ed551c3d13e19208aa6510e90d" } } ], "extra": [ 1, 1, 79, 37, 78, 224, 254, 76, 86, 19, 7, 73, 124, 43, 95, 231, 162, 201, 185, 47, 147, 178, 126, 152, 18, 174, 201, 48, 36, 4, 164, 183, 19, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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