Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 956a136a23bb8df13ae997436e653887029504c6968a5387b061f116662efbda

Tx prefix hash: 970c958928692279ff90ae54b6e65c477f87e872fbfde20b59b2b83cd59948ad
Tx public key: 1511ce65fda2b9369e6aad21b6c0691ae97942b63f76a5affc43ec1cb9860a7c
Timestamp: 1690623064 Timestamp [UCT]: 2023-07-29 09:31:04 Age [y:d:h:m:s]: 01:174:01:26:11
Block: 814274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385705 RingCT/type: yes/0
Extra: 011511ce65fda2b9369e6aad21b6c0691ae97942b63f76a5affc43ec1cb9860a7c021100000002faf35c9c000000000000000000

1 output(s) for total of 1.230190378000 dcy

stealth address amount amount idx
00: fd4faa5897d260e603f0f17d7854d3c5547baeecaa69ae8b2e708f6b326064b7 1.230190378000 1266035 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": 814284, "vin": [ { "gen": { "height": 814274 } } ], "vout": [ { "amount": 1230190378, "target": { "key": "fd4faa5897d260e603f0f17d7854d3c5547baeecaa69ae8b2e708f6b326064b7" } } ], "extra": [ 1, 21, 17, 206, 101, 253, 162, 185, 54, 158, 106, 173, 33, 182, 192, 105, 26, 233, 121, 66, 182, 63, 118, 165, 175, 252, 67, 236, 28, 185, 134, 10, 124, 2, 17, 0, 0, 0, 2, 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