Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f97e426db4047148e0fbf9284f66ec84d2edaf9dda6fc9f140523860cef5691

Tx prefix hash: 9b4f552267e585711dfcb8b14397da8bcdf533f96a673da97777ceffcac34e44
Tx public key: 833e23a92826e926f5702c963f7df5c02851dbd95a3c7c1a369df89f6fa15501
Timestamp: 1670692315 Timestamp [UCT]: 2022-12-10 17:11:55 Age [y:d:h:m:s]: 02:165:12:36:08
Block: 649663 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 640043 RingCT/type: yes/0
Extra: 01833e23a92826e926f5702c963f7df5c02851dbd95a3c7c1a369df89f6fa155010211000000017e406890000000000000000000

1 output(s) for total of 4.319135014000 dcy

stealth address amount amount idx
00: bbf818c8574f78302de751c602cd9dfc171d2de25dbd1117d0ec56076aa03053 4.319135014000 1090030 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": 649673, "vin": [ { "gen": { "height": 649663 } } ], "vout": [ { "amount": 4319135014, "target": { "key": "bbf818c8574f78302de751c602cd9dfc171d2de25dbd1117d0ec56076aa03053" } } ], "extra": [ 1, 131, 62, 35, 169, 40, 38, 233, 38, 245, 112, 44, 150, 63, 125, 245, 192, 40, 81, 219, 217, 90, 60, 124, 26, 54, 157, 248, 159, 111, 161, 85, 1, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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