Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a86575237c74f0515b7a44b1517c245e28bf9db07c42d3f4e9e651f9c800403

Tx prefix hash: e4a86cfb72d0bb5be7383fbf8954a5d038c1c5a08da91518cca6f6bb57983360
Tx public key: 025545eb50181d9af7dbfb0760651558d5c810ed0228e933253f2cd8e3e0544f
Timestamp: 1765296508 Timestamp [UCT]: 2025-12-09 16:08:28 Age [y:d:h:m:s]: 00:024:21:37:18
Block: 1429947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17840 RingCT/type: yes/0
Extra: 01025545eb50181d9af7dbfb0760651558d5c810ed0228e933253f2cd8e3e0544f02110000001670609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e3da16582343c42515144c3a81bc68e6ee5cca9dfdf84533c4f332d7d6f94ea 0.600000000000 1918680 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": 1429957, "vin": [ { "gen": { "height": 1429947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e3da16582343c42515144c3a81bc68e6ee5cca9dfdf84533c4f332d7d6f94ea" } } ], "extra": [ 1, 2, 85, 69, 235, 80, 24, 29, 154, 247, 219, 251, 7, 96, 101, 21, 88, 213, 200, 16, 237, 2, 40, 233, 51, 37, 63, 44, 216, 227, 224, 84, 79, 2, 17, 0, 0, 0, 22, 112, 96, 157, 3, 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