Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ab6a8b82f2fcc9309ae6df2ccaeb0b55ed3d9771dac8daf610fc0ac6ee61c98

Tx prefix hash: f6427468db82c9d74f503e95ca93f2583e4ec8d7b88da98bc1a3107b77be9442
Tx public key: 71b992f928c9cf5edc03c5d4f039683d45ed5bb13189c0a7f324970bd1e92d60
Timestamp: 1577980060 Timestamp [UCT]: 2020-01-02 15:47:40 Age [y:d:h:m:s]: 05:100:09:27:52
Block: 37318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1221477 RingCT/type: yes/0
Extra: 0171b992f928c9cf5edc03c5d4f039683d45ed5bb13189c0a7f324970bd1e92d6002110000001fd81c26c0000000000000000000

1 output(s) for total of 461.690380686000 dcy

stealth address amount amount idx
00: 5c87ea0b2106bd497dafaf141c3e2b5bc25e54b4ea4e2bab1512f903b72618ca 461.690380686000 63296 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": 37328, "vin": [ { "gen": { "height": 37318 } } ], "vout": [ { "amount": 461690380686, "target": { "key": "5c87ea0b2106bd497dafaf141c3e2b5bc25e54b4ea4e2bab1512f903b72618ca" } } ], "extra": [ 1, 113, 185, 146, 249, 40, 201, 207, 94, 220, 3, 197, 212, 240, 57, 104, 61, 69, 237, 91, 177, 49, 137, 192, 167, 243, 36, 151, 11, 209, 233, 45, 96, 2, 17, 0, 0, 0, 31, 216, 28, 38, 192, 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