Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce5399cfc54cc8a01c7a20902426d36f9e3afce2a8f3d8020ae5aa1051af6326

Tx prefix hash: a0e533149ebc1bac2f57ceb42f87eadf672705d177f258f148ab7414906b32be
Tx public key: aa8eb38914bb2522594fd4690d630bf1c3d3cfe26b21ccb48a7a3357b917834a
Timestamp: 1759861114 Timestamp [UCT]: 2025-10-07 18:18:34 Age [y:d:h:m:s]: 00:037:10:27:24
Block: 1384897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26815 RingCT/type: yes/0
Extra: 01aa8eb38914bb2522594fd4690d630bf1c3d3cfe26b21ccb48a7a3357b917834a021100000006a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99b2bf36f6ec95833e128317ba4f152cadb2d1fc7d3254cfd9bb0b8967d1bcc6 0.600000000000 1873054 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": 1384907, "vin": [ { "gen": { "height": 1384897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99b2bf36f6ec95833e128317ba4f152cadb2d1fc7d3254cfd9bb0b8967d1bcc6" } } ], "extra": [ 1, 170, 142, 179, 137, 20, 187, 37, 34, 89, 79, 212, 105, 13, 99, 11, 241, 195, 211, 207, 226, 107, 33, 204, 180, 138, 122, 51, 87, 185, 23, 131, 74, 2, 17, 0, 0, 0, 6, 165, 220, 205, 121, 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