Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f03206137797750d6705dd5036879d046103e19cce9a51d02efc6b288c6d198

Tx prefix hash: cc9454d543a387727b44b4dadb7e976b7344fef3c51a2f13d9df7957dcc8772c
Tx public key: 66945763fdf6759df22a2fd601bbdd4c2e62c8cf6ed23b5e41230c06b6c0e911
Timestamp: 1580811900 Timestamp [UCT]: 2020-02-04 10:25:00 Age [y:d:h:m:s]: 05:123:12:23:08
Block: 58603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1240181 RingCT/type: yes/0
Extra: 0166945763fdf6759df22a2fd601bbdd4c2e62c8cf6ed23b5e41230c06b6c0e9110211000000054943cd9f000000000000000000

1 output(s) for total of 392.486527842000 dcy

stealth address amount amount idx
00: 52a76af7b3fd8a7173a9f949701867d21fdc622b1ff57acf570b3d7ff5a28f3e 392.486527842000 108253 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": 58613, "vin": [ { "gen": { "height": 58603 } } ], "vout": [ { "amount": 392486527842, "target": { "key": "52a76af7b3fd8a7173a9f949701867d21fdc622b1ff57acf570b3d7ff5a28f3e" } } ], "extra": [ 1, 102, 148, 87, 99, 253, 246, 117, 157, 242, 42, 47, 214, 1, 187, 221, 76, 46, 98, 200, 207, 110, 210, 59, 94, 65, 35, 12, 6, 182, 192, 233, 17, 2, 17, 0, 0, 0, 5, 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