Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b9722e2d0c2d908ef1de34fe238d1d3f95532dbec023e700f4e8ea22c52d40d

Tx prefix hash: 4222dd98b6de10cff19b6c5bb2cc3154e14b354c711d8d593c6be59e384010c3
Tx public key: a20f4cea88c8e8c494ef3f81f6174190ec19860661aff884198439f2b1e6a0cc
Timestamp: 1702640102 Timestamp [UCT]: 2023-12-15 11:35:02 Age [y:d:h:m:s]: 02:040:00:28:17
Block: 913631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548286 RingCT/type: yes/0
Extra: 01a20f4cea88c8e8c494ef3f81f6174190ec19860661aff884198439f2b1e6a0cc02110000000d33af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ad953e4d206c2f39f661859fc632c728bd2e940d0d9be6a540f51c4f300c952 0.600000000000 1370907 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": 913641, "vin": [ { "gen": { "height": 913631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ad953e4d206c2f39f661859fc632c728bd2e940d0d9be6a540f51c4f300c952" } } ], "extra": [ 1, 162, 15, 76, 234, 136, 200, 232, 196, 148, 239, 63, 129, 246, 23, 65, 144, 236, 25, 134, 6, 97, 175, 248, 132, 25, 132, 57, 242, 177, 230, 160, 204, 2, 17, 0, 0, 0, 13, 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