Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 341c4d6a9d70c5793350901ce247221ca7ed99ead456006abec2c5f1727b602c

Tx prefix hash: 854a61932c1a7320934e98f1d3ab1f43fbd133bcb46765a725731ba624a3092e
Tx public key: cf24ecbf0c6985f065ec1b47aa0ade1e480b47a0d81eaae1379b1f4ff4726397
Timestamp: 1701591849 Timestamp [UCT]: 2023-12-03 08:24:09 Age [y:d:h:m:s]: 01:044:12:31:26
Block: 904943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293184 RingCT/type: yes/0
Extra: 01cf24ecbf0c6985f065ec1b47aa0ade1e480b47a0d81eaae1379b1f4ff472639702110000000875e3f0e9000000000000000000

1 output(s) for total of 0.615953826000 dcy

stealth address amount amount idx
00: 4d04201b9d6e5aab8ed31f758d988b8b3aa5f7f51197a7caec0a2d6ea581d0e1 0.615953826000 1361756 of 0

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": 904953, "vin": [ { "gen": { "height": 904943 } } ], "vout": [ { "amount": 615953826, "target": { "key": "4d04201b9d6e5aab8ed31f758d988b8b3aa5f7f51197a7caec0a2d6ea581d0e1" } } ], "extra": [ 1, 207, 36, 236, 191, 12, 105, 133, 240, 101, 236, 27, 71, 170, 10, 222, 30, 72, 11, 71, 160, 216, 30, 170, 225, 55, 155, 31, 79, 244, 114, 99, 151, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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