Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8881663450d8999e13de083a10819b4fd8946d99a57a4b71a08dffa094644ce

Tx prefix hash: d1164083dcf7efeb158753f46b57de360d211be188b62aa163f09a19d5fd0d28
Tx public key: df7a213731e410b32d051fbcf97a5d9317053fc2044f7d1ae8c50555ff209c8e
Timestamp: 1749002461 Timestamp [UCT]: 2025-06-04 02:01:01 Age [y:d:h:m:s]: 00:159:02:11:12
Block: 1297464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111372 RingCT/type: yes/0
Extra: 01df7a213731e410b32d051fbcf97a5d9317053fc2044f7d1ae8c50555ff209c8e021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe4b574db0bf69050fe6a631a03eb28e3bf653ab84e01aae20000fd509c5a72e 0.600000000000 1784983 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": 1297474, "vin": [ { "gen": { "height": 1297464 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe4b574db0bf69050fe6a631a03eb28e3bf653ab84e01aae20000fd509c5a72e" } } ], "extra": [ 1, 223, 122, 33, 55, 49, 228, 16, 179, 45, 5, 31, 188, 249, 122, 93, 147, 23, 5, 63, 194, 4, 79, 125, 26, 232, 197, 5, 85, 255, 32, 156, 142, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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