Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb0e396cf42923eb2f7877463170c5fa9497aa6305e7b0c049d5a1020214921f

Tx prefix hash: e9211ff04bfeba97e964321437548ed71979ec94d36e122136012e5ee3cf327a
Tx public key: 8e52d7fe44d8e2d8d5acefc9d27b5ccfb4d4ef2c8831d8488355dacb0cca4634
Timestamp: 1726470527 Timestamp [UCT]: 2024-09-16 07:08:47 Age [y:d:h:m:s]: 00:116:05:13:31
Block: 1111194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83106 RingCT/type: yes/0
Extra: 018e52d7fe44d8e2d8d5acefc9d27b5ccfb4d4ef2c8831d8488355dacb0cca463402110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59b6f3f3f4e57a02d2e6429b50fcaa64859699f74a208f50129c1afb55375534 0.600000000000 1590069 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": 1111204, "vin": [ { "gen": { "height": 1111194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59b6f3f3f4e57a02d2e6429b50fcaa64859699f74a208f50129c1afb55375534" } } ], "extra": [ 1, 142, 82, 215, 254, 68, 216, 226, 216, 213, 172, 239, 201, 210, 123, 92, 207, 180, 212, 239, 44, 136, 49, 216, 72, 131, 85, 218, 203, 12, 202, 70, 52, 2, 17, 0, 0, 0, 11, 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