Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 071a1d13fefcb698186b978aad4142a5e22c5d55f5e18d3b9083734e33bcce5b

Tx prefix hash: 1b82cc8ef525814c185591369e626246eb0757e558525ee545d5060141ee0cf5
Tx public key: 9fbf433a42c12b96a38dc79a9e92c7d8395f43391a351569bdcc3a0f9d0409ad
Timestamp: 1708195862 Timestamp [UCT]: 2024-02-17 18:51:02 Age [y:d:h:m:s]: 01:039:09:31:17
Block: 959691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289180 RingCT/type: yes/0
Extra: 019fbf433a42c12b96a38dc79a9e92c7d8395f43391a351569bdcc3a0f9d0409ad02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 033b7b257920ecb7b5aee5ad7c68fa17bc5424cc9f54314a46cdd3e2b5dfa19a 0.600000000000 1419244 of 15

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": 959701, "vin": [ { "gen": { "height": 959691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "033b7b257920ecb7b5aee5ad7c68fa17bc5424cc9f54314a46cdd3e2b5dfa19a" } } ], "extra": [ 1, 159, 191, 67, 58, 66, 193, 43, 150, 163, 141, 199, 154, 158, 146, 199, 216, 57, 95, 67, 57, 26, 53, 21, 105, 189, 204, 58, 15, 157, 4, 9, 173, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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