Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cec686a3ef96515939e55d61422c81bb327ea8dce228468f2b2ed4449f217846

Tx prefix hash: ae6b0d3c343ba167af2ea9c8c40da411a09c657061453ae68dc4852c173223e0
Tx public key: 025669952fd1164c2d4bca9b096d1535807c5783b2a3233030f793031702858b
Timestamp: 1700832973 Timestamp [UCT]: 2023-11-24 13:36:13 Age [y:d:h:m:s]: 01:097:18:40:32
Block: 898652 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331023 RingCT/type: yes/0
Extra: 01025669952fd1164c2d4bca9b096d1535807c5783b2a3233030f793031702858b02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.646238550000 dcy

stealth address amount amount idx
00: c8b7ab37119edca2549b35bcd5652e0b88f51966b206c14eb66252e475aa4c16 0.646238550000 1355079 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": 898662, "vin": [ { "gen": { "height": 898652 } } ], "vout": [ { "amount": 646238550, "target": { "key": "c8b7ab37119edca2549b35bcd5652e0b88f51966b206c14eb66252e475aa4c16" } } ], "extra": [ 1, 2, 86, 105, 149, 47, 209, 22, 76, 45, 75, 202, 155, 9, 109, 21, 53, 128, 124, 87, 131, 178, 163, 35, 48, 48, 247, 147, 3, 23, 2, 133, 139, 2, 17, 0, 0, 0, 4, 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