Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4390e01c39624c941231c9b97884fc3f1b950026779c731c4c71ff4d6281977d

Tx prefix hash: 201eedbce5bcff3fb4516ba058fb901a931bdc4b593d3b6a54bef6e8def29f98
Tx public key: 38ade919f8bdeada560cf478e49b2fad397a0e5b1ab6e5ac93f3f63cfd6b49b7
Timestamp: 1707873392 Timestamp [UCT]: 2024-02-14 01:16:32 Age [y:d:h:m:s]: 01:053:13:59:08
Block: 957016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299334 RingCT/type: yes/0
Extra: 0138ade919f8bdeada560cf478e49b2fad397a0e5b1ab6e5ac93f3f63cfd6b49b702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4ab70c37490e1f839499189fd00509b1cc030f9e5f053c49880416d29085cbc 0.600000000000 1416330 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": 957026, "vin": [ { "gen": { "height": 957016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4ab70c37490e1f839499189fd00509b1cc030f9e5f053c49880416d29085cbc" } } ], "extra": [ 1, 56, 173, 233, 25, 248, 189, 234, 218, 86, 12, 244, 120, 228, 155, 47, 173, 57, 122, 14, 91, 26, 182, 229, 172, 147, 243, 246, 60, 253, 107, 73, 183, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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