Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 165dd1965ce78a82ba2d52d71ba1627f1e8ccdfea5de8d84a2d2b853925c91d7

Tx prefix hash: e11c1180308a6482a897c6f443d2070aab1a46f1591e553d883a69ed037c62f8
Tx public key: 7068fa124766028bc51a172785a2c2adfdde89883eeeabc72bbd9a056a7c26a8
Timestamp: 1695961185 Timestamp [UCT]: 2023-09-29 04:19:45 Age [y:d:h:m:s]: 01:235:18:09:22
Block: 858471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 429580 RingCT/type: yes/0
Extra: 017068fa124766028bc51a172785a2c2adfdde89883eeeabc72bbd9a056a7c26a8021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.878070230000 dcy

stealth address amount amount idx
00: 46db9f920bc43e3b76d6ba24da33163d14d959adc37994d1b7e72718f9ee4209 0.878070230000 1312647 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": 858481, "vin": [ { "gen": { "height": 858471 } } ], "vout": [ { "amount": 878070230, "target": { "key": "46db9f920bc43e3b76d6ba24da33163d14d959adc37994d1b7e72718f9ee4209" } } ], "extra": [ 1, 112, 104, 250, 18, 71, 102, 2, 139, 197, 26, 23, 39, 133, 162, 194, 173, 253, 222, 137, 136, 62, 238, 171, 199, 43, 189, 154, 5, 106, 124, 38, 168, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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