Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4398a68574a1730e2cea6ab53ad4e98eb2f8b22ee264c5a5780a21c894a5b3d9

Tx prefix hash: 27d9c0cb1ba569b5c1f91a301129e320ac97f76ca6e481d2a4ed6e13eb6be977
Tx public key: 6114ad7019c490db14424bce30930e3a00ab9c2101ef0176bdf87309bc3f874c
Timestamp: 1708529286 Timestamp [UCT]: 2024-02-21 15:28:06 Age [y:d:h:m:s]: 01:038:15:28:59
Block: 962454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288636 RingCT/type: yes/0
Extra: 016114ad7019c490db14424bce30930e3a00ab9c2101ef0176bdf87309bc3f874c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdb027ae7b28005ecd6fddedf13527322accbcaf4d058c0e3c61571cf8b1cb4a 0.600000000000 1422091 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": 962464, "vin": [ { "gen": { "height": 962454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdb027ae7b28005ecd6fddedf13527322accbcaf4d058c0e3c61571cf8b1cb4a" } } ], "extra": [ 1, 97, 20, 173, 112, 25, 196, 144, 219, 20, 66, 75, 206, 48, 147, 14, 58, 0, 171, 156, 33, 1, 239, 1, 118, 189, 248, 115, 9, 188, 63, 135, 76, 2, 17, 0, 0, 0, 2, 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