Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bebf0e2d229f24d5ed5fdb45a2065737250099c533059b78ba4a373670b2b7aa

Tx prefix hash: 403556b3e4f55c875296d35270f825bd08f9aa93f0af636d7664762e419d5fcb
Tx public key: cb64eb56d917b352c16e84527e172a56100145a49dd23a2a2ecca5770d901ba0
Timestamp: 1701600846 Timestamp [UCT]: 2023-12-03 10:54:06 Age [y:d:h:m:s]: 01:082:05:26:00
Block: 905013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319878 RingCT/type: yes/0
Extra: 01cb64eb56d917b352c16e84527e172a56100145a49dd23a2a2ecca5770d901ba0021100000006faf35c9c000000000000000000

1 output(s) for total of 0.615624958000 dcy

stealth address amount amount idx
00: 667bc29fc9141287751cdf7f7f39e160868b1a5aaebbb4ef51f61ac731e7dc3f 0.615624958000 1361836 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": 905023, "vin": [ { "gen": { "height": 905013 } } ], "vout": [ { "amount": 615624958, "target": { "key": "667bc29fc9141287751cdf7f7f39e160868b1a5aaebbb4ef51f61ac731e7dc3f" } } ], "extra": [ 1, 203, 100, 235, 86, 217, 23, 179, 82, 193, 110, 132, 82, 126, 23, 42, 86, 16, 1, 69, 164, 157, 210, 58, 42, 46, 204, 165, 119, 13, 144, 27, 160, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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