Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 395f0aaf05b41407ca3db604050808d81b66738768df3a49a3f5c3aa705d18a5

Tx prefix hash: c9319c8f4d2a425f98f6a744b6ad2130f12530b9b7c9829ef74c77e05886ce3e
Tx public key: 4cc727d3706a8b8ec8cdbee42666fe9e71f6d73c19ab9b184e5fc8618681ecc6
Timestamp: 1702387289 Timestamp [UCT]: 2023-12-12 13:21:29 Age [y:d:h:m:s]: 01:155:12:14:57
Block: 911557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372275 RingCT/type: yes/0
Extra: 014cc727d3706a8b8ec8cdbee42666fe9e71f6d73c19ab9b184e5fc8618681ecc602110000000575e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d90a5f153967024b05a84ba7ba1faa5969950064f7cb1fc1fb9a5034d1f33b6 0.600000000000 1368769 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": 911567, "vin": [ { "gen": { "height": 911557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d90a5f153967024b05a84ba7ba1faa5969950064f7cb1fc1fb9a5034d1f33b6" } } ], "extra": [ 1, 76, 199, 39, 211, 112, 106, 139, 142, 200, 205, 190, 228, 38, 102, 254, 158, 113, 246, 215, 60, 25, 171, 155, 24, 78, 95, 200, 97, 134, 129, 236, 198, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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