Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a57a7eba468e6fe48745949930565874a978fdf3faa18c08e70d91c8f4b1eaf

Tx prefix hash: 76295bbf7141a41871b9f09fbfaaae4d0482c2b066e5270ed7e2d7f64ff9edee
Tx public key: b5a239d45e1d670fcad874c4040f419410e2b281c0aea39d0abc4127ae2f9fab
Timestamp: 1726366138 Timestamp [UCT]: 2024-09-15 02:08:58 Age [y:d:h:m:s]: 00:205:16:12:29
Block: 1110327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146823 RingCT/type: yes/0
Extra: 01b5a239d45e1d670fcad874c4040f419410e2b281c0aea39d0abc4127ae2f9fab021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f839ded60493435a58c323e986b01a0c02cc416e82c0d81b32188d72efef7af8 0.600000000000 1588892 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": 1110337, "vin": [ { "gen": { "height": 1110327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f839ded60493435a58c323e986b01a0c02cc416e82c0d81b32188d72efef7af8" } } ], "extra": [ 1, 181, 162, 57, 212, 94, 29, 103, 15, 202, 216, 116, 196, 4, 15, 65, 148, 16, 226, 178, 129, 192, 174, 163, 157, 10, 188, 65, 39, 174, 47, 159, 171, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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