Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c84e114724eb930c670f8d0b8fd9fbbe6283796e8e909b2c94fdcf32f6c9d3

Tx prefix hash: f23bdcf56d440568c0e1f06cc3e223e30eaab059847bfab09ed53aaec8b7506e
Tx public key: ec9dec2d62299b0f7827ebc4025b69c28fcbc8961fcaeac1901699af4cb4d295
Timestamp: 1694743694 Timestamp [UCT]: 2023-09-15 02:08:14 Age [y:d:h:m:s]: 01:204:04:24:29
Block: 848348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407029 RingCT/type: yes/0
Extra: 01ec9dec2d62299b0f7827ebc4025b69c28fcbc8961fcaeac1901699af4cb4d2950211000000054b8f5122000000000000000000

1 output(s) for total of 0.948573459000 dcy

stealth address amount amount idx
00: 8b791bc99d04d0e94b2d6e358444331503b571c79f769f622517df560a28baab 0.948573459000 1301944 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": 848358, "vin": [ { "gen": { "height": 848348 } } ], "vout": [ { "amount": 948573459, "target": { "key": "8b791bc99d04d0e94b2d6e358444331503b571c79f769f622517df560a28baab" } } ], "extra": [ 1, 236, 157, 236, 45, 98, 41, 155, 15, 120, 39, 235, 196, 2, 91, 105, 194, 143, 203, 200, 150, 31, 202, 234, 193, 144, 22, 153, 175, 76, 180, 210, 149, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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