Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09ba244b7fbead74721f82a7f71a86a7cdb6b2feec3eac63f48002de6edc26bc

Tx prefix hash: fd40e4514692a25d97a3c32b6c876c0d46c760aeb76ba87bc961d8667dd12456
Tx public key: 736964fd3a33b88492506e2414d09bef7ad9f3d2be17d53a705e2e45e0bdcf36
Timestamp: 1758693445 Timestamp [UCT]: 2025-09-24 05:57:25 Age [y:d:h:m:s]: 00:101:01:36:24
Block: 1375222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72380 RingCT/type: yes/0
Extra: 01736964fd3a33b88492506e2414d09bef7ad9f3d2be17d53a705e2e45e0bdcf36021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d06943f5b0fa9e74150ffb9861e709cd5c1d7b00ab9e08ce3773079921e1bd53 0.600000000000 1863307 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": 1375232, "vin": [ { "gen": { "height": 1375222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d06943f5b0fa9e74150ffb9861e709cd5c1d7b00ab9e08ce3773079921e1bd53" } } ], "extra": [ 1, 115, 105, 100, 253, 58, 51, 184, 132, 146, 80, 110, 36, 20, 208, 155, 239, 122, 217, 243, 210, 190, 23, 213, 58, 112, 94, 46, 69, 224, 189, 207, 54, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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