← previous blocknext block →recent activity
Analyzing
Block #93,501,526
16 transactions · 11 stateful · 2026-08-06 01:25:15 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,501,526 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
11w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x3da3a82e…8a6a
0x34b655…2a6f
4 touches
1 conflict
0x4b76146e…0dcb
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x56a919c4…ab49
0x01bff4…1071
2 touches
0 conflicts
0xb1a4d6b6…304f
0x01bff4…1071
2 touches
0 conflicts
0x703b861a…cbe3
0x188d58…ea8e
2 touches
0 conflicts
0x703b861a…cbe4
0x188d58…ea8e
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity