Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f41490a75706e3a32e4ceedfa47db7bcd8c34af5aae000c12eecea6d4baccaa

Tx prefix hash: 348abe6a42df5da63b44465d00f48347a0596a6dcbf59a371bafcb270cb4ab26
Tx public key: a1d7f55c06722ad742562697ad8ffdf19ba2e2a3b9611c8d7add828cf3f08ec2
Timestamp: 1708326425 Timestamp [UCT]: 2024-02-19 07:07:05 Age [y:d:h:m:s]: 00:339:23:25:11
Block: 960777 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243332 RingCT/type: yes/0
Extra: 01a1d7f55c06722ad742562697ad8ffdf19ba2e2a3b9611c8d7add828cf3f08ec202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 100dc8e97a0c3165a56a4b7e9f564d9095cd0358b342b2a4b75cbd54bfa52cf5 0.600000000000 1420364 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": 960787, "vin": [ { "gen": { "height": 960777 } } ], "vout": [ { "amount": 600000000, "target": { "key": "100dc8e97a0c3165a56a4b7e9f564d9095cd0358b342b2a4b75cbd54bfa52cf5" } } ], "extra": [ 1, 161, 215, 245, 92, 6, 114, 42, 215, 66, 86, 38, 151, 173, 143, 253, 241, 155, 162, 226, 163, 185, 97, 28, 141, 122, 221, 130, 140, 243, 240, 142, 194, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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