Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 854893d835f2070edd06d5d74f656cdebaf6bbd0b9ec1ee12256ad2eac396c62

Tx prefix hash: 867b94f60d975d81a27b0411ce9a7f5457d8221b8c0978cab84f5448c8aabc01
Tx public key: 07f57db2b0e432ffd115e26cd68df657e40af278f385af567e4b0e1f506d932e
Timestamp: 1710099468 Timestamp [UCT]: 2024-03-10 19:37:48 Age [y:d:h:m:s]: 01:244:11:36:45
Block: 975484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433444 RingCT/type: yes/0
Extra: 0107f57db2b0e432ffd115e26cd68df657e40af278f385af567e4b0e1f506d932e0211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 844aa9033d6b1a567a7e42e6387c75859ef4204a041bf677fc6e7ec4813a7c76 0.600000000000 1435457 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": 975494, "vin": [ { "gen": { "height": 975484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "844aa9033d6b1a567a7e42e6387c75859ef4204a041bf677fc6e7ec4813a7c76" } } ], "extra": [ 1, 7, 245, 125, 178, 176, 228, 50, 255, 209, 21, 226, 108, 214, 141, 246, 87, 228, 10, 242, 120, 243, 133, 175, 86, 126, 75, 14, 31, 80, 109, 147, 46, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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