Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85311522a9da0941649f0dc40e8dc458267b45d2fa2df7dad7da9407a149c19e

Tx prefix hash: 6ea52d31f1fdf7caea2543b10722b9ca3f9203a8a462a37df901fff2afb3ac52
Tx public key: f5e64e5cb2033840f86f4b32e1240dec1aeb82aa03f5c0935e73e7b62b461135
Timestamp: 1761962123 Timestamp [UCT]: 2025-11-01 01:55:23 Age [y:d:h:m:s]: 00:007:12:50:59
Block: 1402334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5382 RingCT/type: yes/0
Extra: 01f5e64e5cb2033840f86f4b32e1240dec1aeb82aa03f5c0935e73e7b62b4611350211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 847bf54b05cad4948ce46d0e46233d20e0b7a277e58cea0499e8902be0bcd61b 0.600000000000 1890653 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": 1402344, "vin": [ { "gen": { "height": 1402334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "847bf54b05cad4948ce46d0e46233d20e0b7a277e58cea0499e8902be0bcd61b" } } ], "extra": [ 1, 245, 230, 78, 92, 178, 3, 56, 64, 248, 111, 75, 50, 225, 36, 13, 236, 26, 235, 130, 170, 3, 245, 192, 147, 94, 115, 231, 182, 43, 70, 17, 53, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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