Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cff9dc1ac684bbb9253591655983b8d4788b4edb629ec489fabdec1d1e2aa7ab

Tx prefix hash: 69496a70745be7c75778262036ef81f9cd81c14b2d06076f9d95efb9cd8a6b7d
Tx public key: 8564d1e6eba3e56db7abeb7bbd4e8834a1c9bc75c490b6921abfc4d58832b206
Timestamp: 1729916966 Timestamp [UCT]: 2024-10-26 04:29:26 Age [y:d:h:m:s]: 01:096:15:59:01
Block: 1139738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327393 RingCT/type: yes/0
Extra: 018564d1e6eba3e56db7abeb7bbd4e8834a1c9bc75c490b6921abfc4d58832b206021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70707e54d8c7844d1476f6b3d160f5d29a327c13e6bc06351e77600a159d3fbd 0.600000000000 1623525 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": 1139748, "vin": [ { "gen": { "height": 1139738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70707e54d8c7844d1476f6b3d160f5d29a327c13e6bc06351e77600a159d3fbd" } } ], "extra": [ 1, 133, 100, 209, 230, 235, 163, 229, 109, 183, 171, 235, 123, 189, 78, 136, 52, 161, 201, 188, 117, 196, 144, 182, 146, 26, 191, 196, 213, 136, 50, 178, 6, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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