Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67d1f611c2247ef8825077b87f53a12d0a7facdd1f84d0db6ef260736a74ba7d

Tx prefix hash: 0fa683d90c7630821f3b39aa774eed377a6f87b69131003d6e4058eb35b0536b
Tx public key: fd76989eeaefae99ca308352e42c2282af4cb89a97b3dc383b4a2e3c09c0d657
Timestamp: 1730607155 Timestamp [UCT]: 2024-11-03 04:12:35 Age [y:d:h:m:s]: 00:143:08:52:37
Block: 1145406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102289 RingCT/type: yes/0
Extra: 01fd76989eeaefae99ca308352e42c2282af4cb89a97b3dc383b4a2e3c09c0d6570211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cf3e2321a947ff54484dd4601461c68c17c2e2a30f2d562c7bedf80948aa133 0.600000000000 1629837 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": 1145416, "vin": [ { "gen": { "height": 1145406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cf3e2321a947ff54484dd4601461c68c17c2e2a30f2d562c7bedf80948aa133" } } ], "extra": [ 1, 253, 118, 152, 158, 234, 239, 174, 153, 202, 48, 131, 82, 228, 44, 34, 130, 175, 76, 184, 154, 151, 179, 220, 56, 59, 74, 46, 60, 9, 192, 214, 87, 2, 17, 0, 0, 0, 6, 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