Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0db532d3e3cc619966f4a2391da949e72aa011f22b4709cf36f4f92468206d9b

Tx prefix hash: ccfb412296a2e46089f2e6cb0944689c3dc61d6ca71a5edb7780708a315df80f
Tx public key: 0cba81553d2efeab6d54acb38b8ac8dfac37e6347e3d74b750c1c19bf0214564
Timestamp: 1732958897 Timestamp [UCT]: 2024-11-30 09:28:17 Age [y:d:h:m:s]: 00:114:14:42:55
Block: 1164894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81706 RingCT/type: yes/0
Extra: 010cba81553d2efeab6d54acb38b8ac8dfac37e6347e3d74b750c1c19bf0214564021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb51549326d01d0f1f7b2aed0a203025277490ffc901345dd80e922b162b9758 0.600000000000 1650569 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": 1164904, "vin": [ { "gen": { "height": 1164894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb51549326d01d0f1f7b2aed0a203025277490ffc901345dd80e922b162b9758" } } ], "extra": [ 1, 12, 186, 129, 85, 61, 46, 254, 171, 109, 84, 172, 179, 139, 138, 200, 223, 172, 55, 230, 52, 126, 61, 116, 183, 80, 193, 193, 155, 240, 33, 69, 100, 2, 17, 0, 0, 0, 3, 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