Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aca1ab2a80df3a1e5cfe71b6a431aab60dd1def0b619577ca00211ca900abc94

Tx prefix hash: 5a1ec5ee7fec009de788b4ca05bc9c08828e2c32f2cfdb1967e21e7aabc98f1a
Tx public key: 25db911cdaa10d704ee1ba1ab941f3b961ee85e2ec5a7b351e0c5dcfb730c321
Timestamp: 1721949734 Timestamp [UCT]: 2024-07-25 23:22:14 Age [y:d:h:m:s]: 00:279:23:11:57
Block: 1073715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200020 RingCT/type: yes/0
Extra: 0125db911cdaa10d704ee1ba1ab941f3b961ee85e2ec5a7b351e0c5dcfb730c32102110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1763372b01a567a43986f37a4a1194ae0bd39653e1d6adc6a90ac8950e33eeb7 0.600000000000 1546222 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": 1073725, "vin": [ { "gen": { "height": 1073715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1763372b01a567a43986f37a4a1194ae0bd39653e1d6adc6a90ac8950e33eeb7" } } ], "extra": [ 1, 37, 219, 145, 28, 218, 161, 13, 112, 78, 225, 186, 26, 185, 65, 243, 185, 97, 238, 133, 226, 236, 90, 123, 53, 30, 12, 93, 207, 183, 48, 195, 33, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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