Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9e2b0b0c8a14ccc4c27fff4179b3f68b105b310b4abeceaaa492331939c7903

Tx prefix hash: 965f94b112efc53165dc7bc31d3684e9177dc5c58d4f007d6b459d23030ecf82
Tx public key: d323d438a6dc1b51edb9a487d4e371713ecd4e280b7e6e63ca2d9dc5db2c8e74
Timestamp: 1724658607 Timestamp [UCT]: 2024-08-26 07:50:07 Age [y:d:h:m:s]: 00:090:11:34:45
Block: 1096170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64722 RingCT/type: yes/0
Extra: 01d323d438a6dc1b51edb9a487d4e371713ecd4e280b7e6e63ca2d9dc5db2c8e7402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7edb3c88923043e223dce2fdcb43d704d4b32f9f74272fbcc73b1b9790ab50c 0.600000000000 1571357 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": 1096180, "vin": [ { "gen": { "height": 1096170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7edb3c88923043e223dce2fdcb43d704d4b32f9f74272fbcc73b1b9790ab50c" } } ], "extra": [ 1, 211, 35, 212, 56, 166, 220, 27, 81, 237, 185, 164, 135, 212, 227, 113, 113, 62, 205, 78, 40, 11, 126, 110, 99, 202, 45, 157, 197, 219, 44, 142, 116, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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