Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce4200637ca4706fef4c56171f2653c826c412b9fa3640b9e378dfb9fde9d96f

Tx prefix hash: a5b8800ad9da460ad2565a10eb3fdecaefbbda54f7418b8d4ed38359a0354c9c
Tx public key: 9e1bb355d2462688bb6f21ae8c5ffd6d378e1456ce54d714cc048f48bdd1225f
Timestamp: 1737777563 Timestamp [UCT]: 2025-01-25 03:59:23 Age [y:d:h:m:s]: 00:144:03:00:51
Block: 1204741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102754 RingCT/type: yes/0
Extra: 019e1bb355d2462688bb6f21ae8c5ffd6d378e1456ce54d714cc048f48bdd1225f02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab13a4cf777423e068296bec1be4e3b647d103aa25d0d4f8e401bfa5de52e99d 0.600000000000 1691434 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": 1204751, "vin": [ { "gen": { "height": 1204741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab13a4cf777423e068296bec1be4e3b647d103aa25d0d4f8e401bfa5de52e99d" } } ], "extra": [ 1, 158, 27, 179, 85, 210, 70, 38, 136, 187, 111, 33, 174, 140, 95, 253, 109, 55, 142, 20, 86, 206, 84, 215, 20, 204, 4, 143, 72, 189, 209, 34, 95, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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