Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 376685c311f181bfead225a7316929be0d2f30f8b04a0439d4be90135e51bc35

Tx prefix hash: e752f38e9692bfd2ea893914e168c2cb84ccfe44a5f4e450725f5dc815474b2e
Tx public key: 43d90267284d6aa4edcda1381f665095e839f2025ee4abe44c7a593b35f3faf7
Timestamp: 1716062874 Timestamp [UCT]: 2024-05-18 20:07:54 Age [y:d:h:m:s]: 00:308:04:26:44
Block: 1024911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220277 RingCT/type: yes/0
Extra: 0143d90267284d6aa4edcda1381f665095e839f2025ee4abe44c7a593b35f3faf70211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e392a2ca15fa3d8f67b6399987ff3844609918596ae962e67e27bec971b8df5 0.600000000000 1491026 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": 1024921, "vin": [ { "gen": { "height": 1024911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e392a2ca15fa3d8f67b6399987ff3844609918596ae962e67e27bec971b8df5" } } ], "extra": [ 1, 67, 217, 2, 103, 40, 77, 106, 164, 237, 205, 161, 56, 31, 102, 80, 149, 232, 57, 242, 2, 94, 228, 171, 228, 76, 122, 89, 59, 53, 243, 250, 247, 2, 17, 0, 0, 0, 1, 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