Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b52cc6193ea9f8679e5588e8e5662e09de5d0cf2ed5823adb21b7179ec90a975

Tx prefix hash: d97158c05733a1f8a56b39e275c351aed7dda9ac8930c33094566b50edd3456f
Tx public key: c3001b1f40558e2cc1d5d67f60278eb30032a804b10d3e1ccf2a2bb68f0175d9
Timestamp: 1718981085 Timestamp [UCT]: 2024-06-21 14:44:45 Age [y:d:h:m:s]: 00:268:21:48:44
Block: 1049086 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192185 RingCT/type: yes/0
Extra: 01c3001b1f40558e2cc1d5d67f60278eb30032a804b10d3e1ccf2a2bb68f0175d902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 609cec6ab8f52727c08c260f76a557ea6676624ba67cda24b870c67925f37c1c 0.600000000000 1519183 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": 1049096, "vin": [ { "gen": { "height": 1049086 } } ], "vout": [ { "amount": 600000000, "target": { "key": "609cec6ab8f52727c08c260f76a557ea6676624ba67cda24b870c67925f37c1c" } } ], "extra": [ 1, 195, 0, 27, 31, 64, 85, 142, 44, 193, 213, 214, 127, 96, 39, 142, 179, 0, 50, 168, 4, 177, 13, 62, 28, 207, 42, 43, 182, 143, 1, 117, 217, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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