Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e2262915d638333c4a5d2f93938b1937547771c83f5b3d815711bd6f50e47a

Tx prefix hash: e053f78e83b56e2497eca812c4bb1e45ced5c90e2c8f54936c4e950fa850272a
Tx public key: 76d49e6da94a51f359d23b38fd1a411d25820eb525541a506aa744af77f7586c
Timestamp: 1716743064 Timestamp [UCT]: 2024-05-26 17:04:24 Age [y:d:h:m:s]: 00:321:13:41:43
Block: 1030562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229824 RingCT/type: yes/0
Extra: 0176d49e6da94a51f359d23b38fd1a411d25820eb525541a506aa744af77f7586c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9b94953cf0ffc0f103f1f8d2e53f11bc4fe960519c93244146695082f0588ab 0.600000000000 1498819 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": 1030572, "vin": [ { "gen": { "height": 1030562 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9b94953cf0ffc0f103f1f8d2e53f11bc4fe960519c93244146695082f0588ab" } } ], "extra": [ 1, 118, 212, 158, 109, 169, 74, 81, 243, 89, 210, 59, 56, 253, 26, 65, 29, 37, 130, 14, 181, 37, 84, 26, 80, 106, 167, 68, 175, 119, 247, 88, 108, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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