Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ca8c76d857480f0bdfa703184325543c3e8500e2c3e39c9b4c56d91c2d06ed

Tx prefix hash: 1f17adc603b8ff36984915e39129ff0c22543f44fec656714ea4d2ae8a499736
Tx public key: c6d4ff961d75c179840f59dacb75669081d90f23cd0d21fe42584750515ccac0
Timestamp: 1716735370 Timestamp [UCT]: 2024-05-26 14:56:10 Age [y:d:h:m:s]: 00:298:08:02:39
Block: 1030505 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213227 RingCT/type: yes/0
Extra: 01c6d4ff961d75c179840f59dacb75669081d90f23cd0d21fe42584750515ccac002110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd3e910c0df67d6a436e579bc48a6da8dfc3709f292e7b94102b0e7b12f7b609 0.600000000000 1498760 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": 1030515, "vin": [ { "gen": { "height": 1030505 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd3e910c0df67d6a436e579bc48a6da8dfc3709f292e7b94102b0e7b12f7b609" } } ], "extra": [ 1, 198, 212, 255, 150, 29, 117, 193, 121, 132, 15, 89, 218, 203, 117, 102, 144, 129, 217, 15, 35, 205, 13, 33, 254, 66, 88, 71, 80, 81, 92, 202, 192, 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