Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 391fe6ef2119730a6e4ab4c81950d2940c968c7df41918a1d7e99bebcd705817

Tx prefix hash: 68db098230685ea9269ad7898e54096647d733426c66624f1cba1c1a60e1aa84
Tx public key: e7f91c5511cdb632fc4cab73d3c97f5f9734a1d309f8f956c099394767406a1c
Timestamp: 1699822295 Timestamp [UCT]: 2023-11-12 20:51:35 Age [y:d:h:m:s]: 01:202:00:09:12
Block: 890279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405594 RingCT/type: yes/0
Extra: 01e7f91c5511cdb632fc4cab73d3c97f5f9734a1d309f8f956c099394767406a1c0211000000014b8f5122000000000000000000

1 output(s) for total of 0.688868138000 dcy

stealth address amount amount idx
00: 45257cf2a1aea50f5c62ad68d34c9e874fbab376201a3e4ed4e71c7fc718ae20 0.688868138000 1346302 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": 890289, "vin": [ { "gen": { "height": 890279 } } ], "vout": [ { "amount": 688868138, "target": { "key": "45257cf2a1aea50f5c62ad68d34c9e874fbab376201a3e4ed4e71c7fc718ae20" } } ], "extra": [ 1, 231, 249, 28, 85, 17, 205, 182, 50, 252, 76, 171, 115, 211, 201, 127, 95, 151, 52, 161, 211, 9, 248, 249, 86, 192, 153, 57, 71, 103, 64, 106, 28, 2, 17, 0, 0, 0, 1, 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