Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 716edd1154a0709ea0bdf42cb4cc6825d1f2db1997adedefe23eb95411273603

Tx prefix hash: c0985d43c4618b18385b8c7b6f4fc083f9378e324785b6c360368c747445a7fc
Tx public key: e89c74d5d04c857b8d58c77dc95cb9137bb024da07f3e036737df1e1a17596fc
Timestamp: 1577173513 Timestamp [UCT]: 2019-12-24 07:45:13 Age [y:d:h:m:s]: 05:159:02:02:59
Block: 30497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1263623 RingCT/type: yes/0
Extra: 01e89c74d5d04c857b8d58c77dc95cb9137bb024da07f3e036737df1e1a17596fc0211000000034943cd9f000000000000000000

1 output(s) for total of 486.353046526000 dcy

stealth address amount amount idx
00: f6485358b86355fa5e5bd19f997f87133304cfe60851d47fc9abe46b23e31e8d 486.353046526000 50357 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": 30507, "vin": [ { "gen": { "height": 30497 } } ], "vout": [ { "amount": 486353046526, "target": { "key": "f6485358b86355fa5e5bd19f997f87133304cfe60851d47fc9abe46b23e31e8d" } } ], "extra": [ 1, 232, 156, 116, 213, 208, 76, 133, 123, 141, 88, 199, 125, 201, 92, 185, 19, 123, 176, 36, 218, 7, 243, 224, 54, 115, 125, 241, 225, 161, 117, 150, 252, 2, 17, 0, 0, 0, 3, 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