Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae8da5b60ef3bb586c0f515258611cc7099f1007ee2383776fc1cbba6f25342a

Tx prefix hash: d1011a06315143f93c6e22cdd6b33b20d4b4f4792af8c7a0bd4e54fc0fd5059e
Tx public key: bfe71167648632b8d99d0ecf2cf7d2c66b91fbffe88b9b3a1dbdba59da7995bb
Timestamp: 1719222804 Timestamp [UCT]: 2024-06-24 09:53:24 Age [y:d:h:m:s]: 00:279:18:28:32
Block: 1051106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199908 RingCT/type: yes/0
Extra: 01bfe71167648632b8d99d0ecf2cf7d2c66b91fbffe88b9b3a1dbdba59da7995bb0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bf32507d3398f7eec40372649b0cda3f806a620a50e77dc657c23e9061fb4c0 0.600000000000 1521341 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": 1051116, "vin": [ { "gen": { "height": 1051106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bf32507d3398f7eec40372649b0cda3f806a620a50e77dc657c23e9061fb4c0" } } ], "extra": [ 1, 191, 231, 17, 103, 100, 134, 50, 184, 217, 157, 14, 207, 44, 247, 210, 198, 107, 145, 251, 255, 232, 139, 155, 58, 29, 189, 186, 89, 218, 121, 149, 187, 2, 17, 0, 0, 0, 7, 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