Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d550348ab473cd626f98fae7893b75fbe9475b4efe2f0fdb1565289d38a8cf56

Tx prefix hash: b9b87612caf3d1182b1dd1b1c1e3fc7c46d788cc50b938aa3f6583262ad4eeb7
Tx public key: dd587fb95b82fa1b7eb440714d9d51a1a1153b6eaf8004dd7433c87246cf48e0
Timestamp: 1706285485 Timestamp [UCT]: 2024-01-26 16:11:25 Age [y:d:h:m:s]: 01:030:07:33:30
Block: 943833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282716 RingCT/type: yes/0
Extra: 01dd587fb95b82fa1b7eb440714d9d51a1a1153b6eaf8004dd7433c87246cf48e00211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9872ba1f5e88221dcf029870b716e028f7aabfecc8803a72bc21d901d9357c07 0.600000000000 1402059 of 15

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": 943843, "vin": [ { "gen": { "height": 943833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9872ba1f5e88221dcf029870b716e028f7aabfecc8803a72bc21d901d9357c07" } } ], "extra": [ 1, 221, 88, 127, 185, 91, 130, 250, 27, 126, 180, 64, 113, 77, 157, 81, 161, 161, 21, 59, 110, 175, 128, 4, 221, 116, 51, 200, 114, 70, 207, 72, 224, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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