Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02ca62cb9584f72dcb11394ed59d70dafecd37a23a57c18861db98fb4cdae57a

Tx prefix hash: 980ab71bec95bffe0c6ae0d3b2111317e1873f94e830331c8ed14a6ef1c52319
Tx public key: dfbb35db95ee2119c04ca2d4b93612384e41e0cf6546bf67fb80475a2d3a314b
Timestamp: 1706036372 Timestamp [UCT]: 2024-01-23 18:59:32 Age [y:d:h:m:s]: 01:146:06:06:37
Block: 941760 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365553 RingCT/type: yes/0
Extra: 01dfbb35db95ee2119c04ca2d4b93612384e41e0cf6546bf67fb80475a2d3a314b02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a37588429852773fe61ee7b5ba092b283d65c6d851dd3d0a6dd1948c7f832d0 0.600000000000 1399916 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": 941770, "vin": [ { "gen": { "height": 941760 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a37588429852773fe61ee7b5ba092b283d65c6d851dd3d0a6dd1948c7f832d0" } } ], "extra": [ 1, 223, 187, 53, 219, 149, 238, 33, 25, 192, 76, 162, 212, 185, 54, 18, 56, 78, 65, 224, 207, 101, 70, 191, 103, 251, 128, 71, 90, 45, 58, 49, 75, 2, 17, 0, 0, 0, 4, 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