Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a66da7a8909078432ea9c0e09601d641421d5d71229c0ad4aa1e393e9a1a7fe

Tx prefix hash: eb44a1ee6cfaeea7375fbae9a4b4e5ac67551d224336a3f50213745dad41fa14
Tx public key: 4af573fc3fe91406423f8dd1a0185ae48ea157789712903f72fd8b0fdb1a1596
Timestamp: 1725047738 Timestamp [UCT]: 2024-08-30 19:55:38 Age [y:d:h:m:s]: 00:225:02:24:22
Block: 1099403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160735 RingCT/type: yes/0
Extra: 014af573fc3fe91406423f8dd1a0185ae48ea157789712903f72fd8b0fdb1a1596021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56dcd1a3fac138bf8e9103307079a8bd5ba6821eef32ae6ba331a8c9ffd106d0 0.600000000000 1575364 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": 1099413, "vin": [ { "gen": { "height": 1099403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56dcd1a3fac138bf8e9103307079a8bd5ba6821eef32ae6ba331a8c9ffd106d0" } } ], "extra": [ 1, 74, 245, 115, 252, 63, 233, 20, 6, 66, 63, 141, 209, 160, 24, 90, 228, 142, 161, 87, 120, 151, 18, 144, 63, 114, 253, 139, 15, 219, 26, 21, 150, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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