Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9342aff56563490a2dea758e69f6fd4d0fb3b748f75996f32b6f56b2000525e

Tx prefix hash: 3c03b9d00598201d2519cd7fd07a269adc05aee0916d0cf1b2ce9c03e4ffdf3f
Tx public key: e1b768ad82cbc475fe84fab7c6b6a433979a1658172e3715f65f339696a21122
Timestamp: 1734396407 Timestamp [UCT]: 2024-12-17 00:46:47 Age [y:d:h:m:s]: 00:023:21:07:22
Block: 1176816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17063 RingCT/type: yes/0
Extra: 01e1b768ad82cbc475fe84fab7c6b6a433979a1658172e3715f65f339696a211220211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ad4dcc1fa7e5cfa0ed8b0d33d3ffcbd2880e78bda237a335b4d80bd5ac20bda 0.600000000000 1663177 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": 1176826, "vin": [ { "gen": { "height": 1176816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad4dcc1fa7e5cfa0ed8b0d33d3ffcbd2880e78bda237a335b4d80bd5ac20bda" } } ], "extra": [ 1, 225, 183, 104, 173, 130, 203, 196, 117, 254, 132, 250, 183, 198, 182, 164, 51, 151, 154, 22, 88, 23, 46, 55, 21, 246, 95, 51, 150, 150, 162, 17, 34, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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