Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8691a5622bd4f76dba9d6df813db80d5ba0d479813c382a37f417b7ba047a662

Tx prefix hash: 5e9fe5e896ea90494aaa3f404ab8ec5afef1708c25dfba51e114311331a7fb2c
Tx public key: bb6bd33128ab42f3f5231e17d969b373fdf3d5be7d68e6d0d324f86b9f0d39dd
Timestamp: 1706031504 Timestamp [UCT]: 2024-01-23 17:38:24 Age [y:d:h:m:s]: 00:310:02:30:39
Block: 941722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222054 RingCT/type: yes/0
Extra: 01bb6bd33128ab42f3f5231e17d969b373fdf3d5be7d68e6d0d324f86b9f0d39dd0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17f8ea8c0b0a44950349cad076c05459f600590d4fc1a97c089de0ef47df2140 0.600000000000 1399878 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": 941732, "vin": [ { "gen": { "height": 941722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17f8ea8c0b0a44950349cad076c05459f600590d4fc1a97c089de0ef47df2140" } } ], "extra": [ 1, 187, 107, 211, 49, 40, 171, 66, 243, 245, 35, 30, 23, 217, 105, 179, 115, 253, 243, 213, 190, 125, 104, 230, 208, 211, 36, 248, 107, 159, 13, 57, 221, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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