Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b32e72ce91283ace925c645f1da1f3a9b4de313703f84a18c30316bccf67fc7

Tx prefix hash: 544339eff54a6e34a3c83a78b30c74d0e3fc801085611cd13bc71e02554f8559
Tx public key: 2b0fe708c6c25b9ca724fd86ddca6dde8ca25c238eff66c976853de3c588c31f
Timestamp: 1734669137 Timestamp [UCT]: 2024-12-20 04:32:17 Age [y:d:h:m:s]: 00:087:07:57:11
Block: 1179077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 62192 RingCT/type: yes/0
Extra: 012b0fe708c6c25b9ca724fd86ddca6dde8ca25c238eff66c976853de3c588c31f021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4010e1d1b88e65f2defd9a8706a9104e0b76a987c1397e3d883649399ae3f830 0.600000000000 1665468 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": 1179087, "vin": [ { "gen": { "height": 1179077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4010e1d1b88e65f2defd9a8706a9104e0b76a987c1397e3d883649399ae3f830" } } ], "extra": [ 1, 43, 15, 231, 8, 198, 194, 91, 156, 167, 36, 253, 134, 221, 202, 109, 222, 140, 162, 92, 35, 142, 255, 102, 201, 118, 133, 61, 227, 197, 136, 195, 31, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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