Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7c8ac5e8ea303c48dfa45840b1e3936248766789163e16694560a9f387b8d5f

Tx prefix hash: 7cec8e37dc5fc5d53e9a7317dc348607657a9d68b70512dc20639329c8f2e190
Tx public key: ee09699888a6f8a65f7aac32617fe1f187936ec99141d93e26cc1266bb104fa0
Timestamp: 1649060313 Timestamp [UCT]: 2022-04-04 08:18:33 Age [y:d:h:m:s]: 02:286:15:49:30
Block: 472867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724642 RingCT/type: yes/0
Extra: 01ee09699888a6f8a65f7aac32617fe1f187936ec99141d93e26cc1266bb104fa0021100000016d3fcec30000000000000000000

1 output(s) for total of 16.641819114000 dcy

stealth address amount amount idx
00: 2cf44cb557e7cf1649854079fe355b184c3d4362c2b1e8383fe6fff36ea9192e 16.641819114000 892564 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": 472877, "vin": [ { "gen": { "height": 472867 } } ], "vout": [ { "amount": 16641819114, "target": { "key": "2cf44cb557e7cf1649854079fe355b184c3d4362c2b1e8383fe6fff36ea9192e" } } ], "extra": [ 1, 238, 9, 105, 152, 136, 166, 248, 166, 95, 122, 172, 50, 97, 127, 225, 241, 135, 147, 110, 201, 145, 65, 217, 62, 38, 204, 18, 102, 187, 16, 79, 160, 2, 17, 0, 0, 0, 22, 211, 252, 236, 48, 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