Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de6f81e0918a7cd0c653aaaccfccd16cb402c3743cf05bc4ede901798927ce3b

Tx prefix hash: 5fa5322ff9644f15bff8b960b7df2f1091e6751c2ab18d966c027ee376dba229
Tx public key: d8bce508f2562618354a9f661be4022c3ffd1397f853c8337b3d17ab09d5ba1e
Timestamp: 1761670754 Timestamp [UCT]: 2025-10-28 16:59:14 Age [y:d:h:m:s]: 00:072:01:55:28
Block: 1399917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 51602 RingCT/type: yes/0
Extra: 01d8bce508f2562618354a9f661be4022c3ffd1397f853c8337b3d17ab09d5ba1e02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 043f31a12f46e8b67873d039d7f3785a71c88b7d7be8b596498c6553dbb37123 0.600000000000 1888224 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": 1399927, "vin": [ { "gen": { "height": 1399917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "043f31a12f46e8b67873d039d7f3785a71c88b7d7be8b596498c6553dbb37123" } } ], "extra": [ 1, 216, 188, 229, 8, 242, 86, 38, 24, 53, 74, 159, 102, 27, 228, 2, 44, 63, 253, 19, 151, 248, 83, 200, 51, 123, 61, 23, 171, 9, 213, 186, 30, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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