Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21b2b2c063818aea01924aba06c41a0622af671020a12c510ed991522fcae509

Tx prefix hash: 8f9499d1b1db36a4fd6fc580a498de1bf6ddab19dc37604b7177a9cf9a4632e8
Tx public key: b3f1328cf5a7c14830916566a47e4a18a2449550a500482041eb3528111999b3
Timestamp: 1711599867 Timestamp [UCT]: 2024-03-28 04:24:27 Age [y:d:h:m:s]: 01:013:23:24:14
Block: 987931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270943 RingCT/type: yes/0
Extra: 01b3f1328cf5a7c14830916566a47e4a18a2449550a500482041eb3528111999b30211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48707cf63b611a4deb4eec6a1e6f80626a331191b7ae3d9f65515c0b7adb8c97 0.600000000000 1448192 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": 987941, "vin": [ { "gen": { "height": 987931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48707cf63b611a4deb4eec6a1e6f80626a331191b7ae3d9f65515c0b7adb8c97" } } ], "extra": [ 1, 179, 241, 50, 140, 245, 167, 193, 72, 48, 145, 101, 102, 164, 126, 74, 24, 162, 68, 149, 80, 165, 0, 72, 32, 65, 235, 53, 40, 17, 25, 153, 179, 2, 17, 0, 0, 0, 4, 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