Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 424b23274aab8c046cf231d47d62eaa747b10acdd42af600ea97ad9e78c3dd35

Tx prefix hash: 00908bfd24c5306c8c09a1246d2f458eddf11174d6bae479871b890b1034d0af
Tx public key: cf77f2271dc10975c3d67882420813c61e4df1e752ba7d4f542e248c730ef903
Timestamp: 1737422122 Timestamp [UCT]: 2025-01-21 01:15:22 Age [y:d:h:m:s]: 00:051:10:37:45
Block: 1201802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36587 RingCT/type: yes/0
Extra: 01cf77f2271dc10975c3d67882420813c61e4df1e752ba7d4f542e248c730ef903021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c8e38697d11ebf63f6a04a5e13c41dc3c7bfca76bcc9f20775996cdbb01413 0.600000000000 1688459 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": 1201812, "vin": [ { "gen": { "height": 1201802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c8e38697d11ebf63f6a04a5e13c41dc3c7bfca76bcc9f20775996cdbb01413" } } ], "extra": [ 1, 207, 119, 242, 39, 29, 193, 9, 117, 195, 214, 120, 130, 66, 8, 19, 198, 30, 77, 241, 231, 82, 186, 125, 79, 84, 46, 36, 140, 115, 14, 249, 3, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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