Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b45cafda6343e1803788bdeecf056403cd965cd2a4697d90b9ce8bdd4b9f250a

Tx prefix hash: f314e6166d7b035523a5cb0952086af8e0b93ff634fdf773b2a39f0f37746b69
Tx public key: 9c07ab4cb4142cd1775dddf8cbedc17fb4ceb5f9ec64864a49fce4ebb1dd7a08
Timestamp: 1757892429 Timestamp [UCT]: 2025-09-14 23:27:09 Age [y:d:h:m:s]: 00:110:14:28:47
Block: 1368592 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79199 RingCT/type: yes/0
Extra: 019c07ab4cb4142cd1775dddf8cbedc17fb4ceb5f9ec64864a49fce4ebb1dd7a08021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe14102305a819f5f0bfd3683d25b8288f09f34e49311afdf7aa131c0e70da6c 0.600000000000 1856643 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": 1368602, "vin": [ { "gen": { "height": 1368592 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe14102305a819f5f0bfd3683d25b8288f09f34e49311afdf7aa131c0e70da6c" } } ], "extra": [ 1, 156, 7, 171, 76, 180, 20, 44, 209, 119, 93, 221, 248, 203, 237, 193, 127, 180, 206, 181, 249, 236, 100, 134, 74, 73, 252, 228, 235, 177, 221, 122, 8, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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