Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d09e64f80502682e4c724ddedf6235ddc32440a5635ce3c489c0a373866ff74e

Tx prefix hash: 046d986edb257dd3ff00bd524af9c9f29937d7a83c45cf72afcc8b9dd7ed40e6
Tx public key: 4bea13d9d78c341daac401d875e82167af4d9e504cccb85dc804bcb8568a80f0
Timestamp: 1699394274 Timestamp [UCT]: 2023-11-07 21:57:54 Age [y:d:h:m:s]: 01:160:08:32:14
Block: 886734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375795 RingCT/type: yes/0
Extra: 014bea13d9d78c341daac401d875e82167af4d9e504cccb85dc804bcb8568a80f00211000000054b8f5122000000000000000000

1 output(s) for total of 0.707753719000 dcy

stealth address amount amount idx
00: bf2e619d829a9514c69ea9d9158b7abdf16e55a26e6f9acc9141205ecab2e711 0.707753719000 1342571 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": 886744, "vin": [ { "gen": { "height": 886734 } } ], "vout": [ { "amount": 707753719, "target": { "key": "bf2e619d829a9514c69ea9d9158b7abdf16e55a26e6f9acc9141205ecab2e711" } } ], "extra": [ 1, 75, 234, 19, 217, 215, 140, 52, 29, 170, 196, 1, 216, 117, 232, 33, 103, 175, 77, 158, 80, 76, 204, 184, 93, 200, 4, 188, 184, 86, 138, 128, 240, 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