Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1635115638049cc976ca85a343e81dde02de6eca8f6ce5bc7b14482a6c4e7642

Tx prefix hash: 968f6d8a5847fcf20b4e2fdc9d6c5df9177c61fd3a0671c2264e9430de7ea8bb
Tx public key: e3e3e99f6fbf66d91fbd46d4015bd290477e86c0b6ad4a92b45ebc2c12a1d88d
Timestamp: 1708704711 Timestamp [UCT]: 2024-02-23 16:11:51 Age [y:d:h:m:s]: 01:082:03:20:17
Block: 963914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319750 RingCT/type: yes/0
Extra: 01e3e3e99f6fbf66d91fbd46d4015bd290477e86c0b6ad4a92b45ebc2c12a1d88d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99c2547c88309ec92f26211135127b6a1bfa3f83dfd2ed6e11f9abb68d8bc4d5 0.600000000000 1423641 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": 963924, "vin": [ { "gen": { "height": 963914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99c2547c88309ec92f26211135127b6a1bfa3f83dfd2ed6e11f9abb68d8bc4d5" } } ], "extra": [ 1, 227, 227, 233, 159, 111, 191, 102, 217, 31, 189, 70, 212, 1, 91, 210, 144, 71, 126, 134, 192, 182, 173, 74, 146, 180, 94, 188, 44, 18, 161, 216, 141, 2, 17, 0, 0, 0, 3, 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