Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0fe1bfdcf5a32cc7d60fdf65353713233e88f13a13fc4eb6ee67d74f413e5b0

Tx prefix hash: cb78da6b96f6f4a109916abf4b090318f6db9c0ad411c6a0091f281c534cafa7
Tx public key: 915685967be521b06cf69aa1e094878e6b673f3c6c2278f22835ff5d3d54d80e
Timestamp: 1577118621 Timestamp [UCT]: 2019-12-23 16:30:21 Age [y:d:h:m:s]: 05:287:10:32:57
Block: 30032 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1352978 RingCT/type: yes/0
Extra: 01915685967be521b06cf69aa1e094878e6b673f3c6c2278f22835ff5d3d54d80e02110000003a4943cd9f000000000000000000

1 output(s) for total of 488.081536724000 dcy

stealth address amount amount idx
00: 6f25281cb971bd5dfdbf21a6250b4c7e01ae7331fd6595a633d4836130daee2e 488.081536724000 49574 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": 30042, "vin": [ { "gen": { "height": 30032 } } ], "vout": [ { "amount": 488081536724, "target": { "key": "6f25281cb971bd5dfdbf21a6250b4c7e01ae7331fd6595a633d4836130daee2e" } } ], "extra": [ 1, 145, 86, 133, 150, 123, 229, 33, 176, 108, 246, 154, 161, 224, 148, 135, 142, 107, 103, 63, 60, 108, 34, 120, 242, 40, 53, 255, 93, 61, 84, 216, 14, 2, 17, 0, 0, 0, 58, 73, 67, 205, 159, 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