Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14f3f4eed6ccdf29fa49afdef1c2ecb067d26bb91207d96e69b99bf7ec72ef2c

Tx prefix hash: 7ecc386e3cc2fbc33acff65f8d667ddbf54b30f32959f5cba500be6b87286ead
Tx public key: 74cc5ec0d7bf78b9bada152b2eb99720c55a2584046e259f3f4aa5ff19de261a
Timestamp: 1728516549 Timestamp [UCT]: 2024-10-09 23:29:09 Age [y:d:h:m:s]: 00:104:16:29:14
Block: 1128160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74790 RingCT/type: yes/0
Extra: 0174cc5ec0d7bf78b9bada152b2eb99720c55a2584046e259f3f4aa5ff19de261a02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8d4bd8676e2dff4343dadff0d843371c33954f74f8d52ea156972ea083245bb 0.600000000000 1610977 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": 1128170, "vin": [ { "gen": { "height": 1128160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8d4bd8676e2dff4343dadff0d843371c33954f74f8d52ea156972ea083245bb" } } ], "extra": [ 1, 116, 204, 94, 192, 215, 191, 120, 185, 186, 218, 21, 43, 46, 185, 151, 32, 197, 90, 37, 132, 4, 110, 37, 159, 63, 74, 165, 255, 25, 222, 38, 26, 2, 17, 0, 0, 0, 8, 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