Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ec66b17a32616f42c1d9ed584928ccd7d47863f4c901db6bfdc2eed16cf79bb

Tx prefix hash: ae8d4fb3f5d214958f5437d26bb7a5e979b3db6783cc0b63911ecbf5f1f8867b
Tx public key: e48510bff9399f89fb0060d480af04fbe0c58fe0a2177c0c21dc569cac5edeb9
Timestamp: 1579014437 Timestamp [UCT]: 2020-01-14 15:07:17 Age [y:d:h:m:s]: 05:295:15:28:12
Block: 45376 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1359233 RingCT/type: yes/0
Extra: 01e48510bff9399f89fb0060d480af04fbe0c58fe0a2177c0c21dc569cac5edeb902110000001d391a8d0e000000000000000000

1 output(s) for total of 434.169006248000 dcy

stealth address amount amount idx
00: 22868e2772184a81db02bea84aca5b7a52fe10689793bbf11810295f9161943b 434.169006248000 82884 of 0

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": 45386, "vin": [ { "gen": { "height": 45376 } } ], "vout": [ { "amount": 434169006248, "target": { "key": "22868e2772184a81db02bea84aca5b7a52fe10689793bbf11810295f9161943b" } } ], "extra": [ 1, 228, 133, 16, 191, 249, 57, 159, 137, 251, 0, 96, 212, 128, 175, 4, 251, 224, 197, 143, 224, 162, 23, 124, 12, 33, 220, 86, 156, 172, 94, 222, 185, 2, 17, 0, 0, 0, 29, 57, 26, 141, 14, 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