Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9498a7ff359144baf2d816638b0052bb9a80b57f92eb563f9fde2b91608fd53

Tx prefix hash: f8435ed26cfcee915af13c4ced92aa9decad4aa8ff3069871e1cb0e10e5c43be
Tx public key: 88ad67e5e59c4ad73e1dc6306b8f08eb0eea810eb8e977bfa85f24dd4f279d39
Timestamp: 1755569104 Timestamp [UCT]: 2025-08-19 02:05:04 Age [y:d:h:m:s]: 00:092:16:08:25
Block: 1349565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66134 RingCT/type: yes/0
Extra: 0188ad67e5e59c4ad73e1dc6306b8f08eb0eea810eb8e977bfa85f24dd4f279d390211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1dd95cbee86fb0a4fbd0676f1fa41ad742c440be40de072ea00db1c3b93b3ae 0.600000000000 1837498 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": 1349575, "vin": [ { "gen": { "height": 1349565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1dd95cbee86fb0a4fbd0676f1fa41ad742c440be40de072ea00db1c3b93b3ae" } } ], "extra": [ 1, 136, 173, 103, 229, 229, 156, 74, 215, 62, 29, 198, 48, 107, 143, 8, 235, 14, 234, 129, 14, 184, 233, 119, 191, 168, 95, 36, 221, 79, 39, 157, 57, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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