Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2630d2e0da82a9c9261bbac878b85fc03c8f258c7a5f8ba756e91564a597feb

Tx prefix hash: fa4dcb7764efd87dce0f748adf99436ab65f80a3b9e63f10884f284d7cb16f13
Tx public key: 4570812ee2a0fdcfdd63a759eef8f906bc9be429e490cbb9858440836a43f3e3
Timestamp: 1657790293 Timestamp [UCT]: 2022-07-14 09:18:13 Age [y:d:h:m:s]: 02:173:06:56:11
Block: 543486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 645213 RingCT/type: yes/0
Extra: 014570812ee2a0fdcfdd63a759eef8f906bc9be429e490cbb9858440836a43f3e302110000000433af99f4000000000000000000

1 output(s) for total of 9.709691064000 dcy

stealth address amount amount idx
00: 9b17941b74a423388b5483065edb9d1152fafca478c11b1ab2e3636e8fb48c10 9.709691064000 974159 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": 543496, "vin": [ { "gen": { "height": 543486 } } ], "vout": [ { "amount": 9709691064, "target": { "key": "9b17941b74a423388b5483065edb9d1152fafca478c11b1ab2e3636e8fb48c10" } } ], "extra": [ 1, 69, 112, 129, 46, 226, 160, 253, 207, 221, 99, 167, 89, 238, 248, 249, 6, 188, 155, 228, 41, 228, 144, 203, 185, 133, 132, 64, 131, 106, 67, 243, 227, 2, 17, 0, 0, 0, 4, 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