Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c062e2705cbb8b36b6206c2d7c35f76431ff1e51969bef16bdf1cd485caa21c

Tx prefix hash: 0b76c6cf74107c2fd4047fb2254a8195bfd46a048350ce26a1ca1a28fad03488
Tx public key: 0aa2c164fdd4691baf53553195e5370b6d253d2356f74620ff2eef7f750ca984
Timestamp: 1709647293 Timestamp [UCT]: 2024-03-05 14:01:33 Age [y:d:h:m:s]: 01:068:16:02:02
Block: 971732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310096 RingCT/type: yes/0
Extra: 010aa2c164fdd4691baf53553195e5370b6d253d2356f74620ff2eef7f750ca98402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0507e21360eafa0890f14b709d67ea16d6d1fd2e1bfa52e6c4840ced0e9e3020 0.600000000000 1431633 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": 971742, "vin": [ { "gen": { "height": 971732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0507e21360eafa0890f14b709d67ea16d6d1fd2e1bfa52e6c4840ced0e9e3020" } } ], "extra": [ 1, 10, 162, 193, 100, 253, 212, 105, 27, 175, 83, 85, 49, 149, 229, 55, 11, 109, 37, 61, 35, 86, 247, 70, 32, 255, 46, 239, 127, 117, 12, 169, 132, 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