Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e983c16f80458233ab4c5524fca35516fd9ef66e142b4108ab0cb85f12387c9f

Tx prefix hash: 5211cd8aa6366fca7f5ea6380fc563c7c6a45a645b888bc9743244db6da2f5de
Tx public key: 39b7a9642321a18e7f751b9492dd9b0c2870db1f7846b1e65aa935789d44454e
Timestamp: 1581951244 Timestamp [UCT]: 2020-02-17 14:54:04 Age [y:d:h:m:s]: 04:357:15:55:01
Block: 66941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147678 RingCT/type: yes/0
Extra: 0139b7a9642321a18e7f751b9492dd9b0c2870db1f7846b1e65aa935789d44454e021100000002026b59f3000000000000000000

1 output(s) for total of 368.316960913000 dcy

stealth address amount amount idx
00: d070d30d721094dcc76c22cf3def90c01aa06b5d66ed7ad2497a0f943337b7a7 368.316960913000 123202 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": 66951, "vin": [ { "gen": { "height": 66941 } } ], "vout": [ { "amount": 368316960913, "target": { "key": "d070d30d721094dcc76c22cf3def90c01aa06b5d66ed7ad2497a0f943337b7a7" } } ], "extra": [ 1, 57, 183, 169, 100, 35, 33, 161, 142, 127, 117, 27, 148, 146, 221, 155, 12, 40, 112, 219, 31, 120, 70, 177, 230, 90, 169, 53, 120, 157, 68, 69, 78, 2, 17, 0, 0, 0, 2, 2, 107, 89, 243, 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