Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59e814a62e678dea3dff89357fdea0b54909b4c5d879624fdf5c1442e7eccfbe

Tx prefix hash: 81d3e5705bcb0ae482d12e9a5eaed6bf900fa81eaded357a6b1bf125da7335a1
Tx public key: a9ec604c1c0a5031895550e1b4f8768d3f68297eb56cceb4d5cd961160f37f69
Timestamp: 1706413565 Timestamp [UCT]: 2024-01-28 03:46:05 Age [y:d:h:m:s]: 01:070:17:42:32
Block: 944896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311627 RingCT/type: yes/0
Extra: 01a9ec604c1c0a5031895550e1b4f8768d3f68297eb56cceb4d5cd961160f37f6902110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea12879dc856ea5c28faf798d6a7093dc817536883ef3203db6c47a703a808d9 0.600000000000 1403192 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": 944906, "vin": [ { "gen": { "height": 944896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea12879dc856ea5c28faf798d6a7093dc817536883ef3203db6c47a703a808d9" } } ], "extra": [ 1, 169, 236, 96, 76, 28, 10, 80, 49, 137, 85, 80, 225, 180, 248, 118, 141, 63, 104, 41, 126, 181, 108, 206, 180, 213, 205, 150, 17, 96, 243, 127, 105, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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