Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce34c930b29e1ac71c04446ed2c09378ce38b8989e0995f066efe0fcdf7d0a1f

Tx prefix hash: 4b2565aadbf6c63a746f952f500575d14f12febfa5c44f7035bfd49275cbbbb7
Tx public key: 54549394f4bd7b0fcb9b17331bfc8ef358b03ce3ef8ce1c397e2cefd5f6e49aa
Timestamp: 1744678351 Timestamp [UCT]: 2025-04-15 00:52:31 Age [y:d:h:m:s]: 00:219:13:37:38
Block: 1261640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154648 RingCT/type: yes/0
Extra: 0154549394f4bd7b0fcb9b17331bfc8ef358b03ce3ef8ce1c397e2cefd5f6e49aa021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11a9ee297b94087af39c1fb57b243f27e21237beffd201398bf6f77e6353726f 0.600000000000 1748813 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": 1261650, "vin": [ { "gen": { "height": 1261640 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11a9ee297b94087af39c1fb57b243f27e21237beffd201398bf6f77e6353726f" } } ], "extra": [ 1, 84, 84, 147, 148, 244, 189, 123, 15, 203, 155, 23, 51, 27, 252, 142, 243, 88, 176, 60, 227, 239, 140, 225, 195, 151, 226, 206, 253, 95, 110, 73, 170, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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