Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 642c6a3ea3c7cdf235b6609d968cce5e955d9f1804742064d379bc5d61245aab

Tx prefix hash: e6d4f89fc08e5c6c2c4b28fde839f0fd3fcdd1c9352ff8ab5dc5b88eafdde045
Tx public key: 73898ddd4159d0d0a70caaeb6b0610a3327ded197e6824532a61974a00683960
Timestamp: 1660480529 Timestamp [UCT]: 2022-08-14 12:35:29 Age [y:d:h:m:s]: 02:228:01:56:00
Block: 565668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 684223 RingCT/type: yes/0
Extra: 0173898ddd4159d0d0a70caaeb6b0610a3327ded197e6824532a61974a0068396002110000000333af99f4000000000000000000

1 output(s) for total of 8.197986624000 dcy

stealth address amount amount idx
00: a285c94d602d2c9387f3eac1bd6fce6f9c00253ad12c4dfb9aba2b0dbc2de82a 8.197986624000 998580 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": 565678, "vin": [ { "gen": { "height": 565668 } } ], "vout": [ { "amount": 8197986624, "target": { "key": "a285c94d602d2c9387f3eac1bd6fce6f9c00253ad12c4dfb9aba2b0dbc2de82a" } } ], "extra": [ 1, 115, 137, 141, 221, 65, 89, 208, 208, 167, 12, 170, 235, 107, 6, 16, 163, 50, 125, 237, 25, 126, 104, 36, 83, 42, 97, 151, 74, 0, 104, 57, 96, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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