Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 361ef93514889765f1c31b6f38c061a64510387ce8c0e50352a3b73c204b3af6

Tx prefix hash: f16ee79ae6c849a6f9b090391e455cf486d3e65d89e9749f0f3a5ed31906c349
Tx public key: 3e61e1df5ef7a56a21aef7c33e3f8318f132ac040135d0faa39d010886d8199b
Timestamp: 1705604121 Timestamp [UCT]: 2024-01-18 18:55:21 Age [y:d:h:m:s]: 01:078:15:13:59
Block: 938188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317299 RingCT/type: yes/0
Extra: 013e61e1df5ef7a56a21aef7c33e3f8318f132ac040135d0faa39d010886d8199b02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8d40d1aff4646c80ef356ea1420eced50a4936ee2ab53b12fc549af9640a8bf 0.600000000000 1396258 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": 938198, "vin": [ { "gen": { "height": 938188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8d40d1aff4646c80ef356ea1420eced50a4936ee2ab53b12fc549af9640a8bf" } } ], "extra": [ 1, 62, 97, 225, 223, 94, 247, 165, 106, 33, 174, 247, 195, 62, 63, 131, 24, 241, 50, 172, 4, 1, 53, 208, 250, 163, 157, 1, 8, 134, 216, 25, 155, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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