← previous blocknext block →recent activity
Analyzing
Block #93,558,185
13 transactions · 12 stateful · 2026-08-06 06:10:04 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,558,185 · 13 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
4w05w18w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37bef14c…a6d5
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xfb8dadd6…5560
0x34b655…2a6f
4 touches
1 conflict
0x3111a64f…eb7f
0x34b655…2a6f
4 touches
1 conflict
0x31ba5616…4601
0x34b655…2a6f
4 touches
1 conflict
0x08c34e36…0f35
0xea1b8e…c5ec
2 touches
0 conflicts
0x57c874be…de5b
0xea1b8e…c5ec
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 0x37bef14cb9…88a6d5
Audit this contract →
← previous block·next block →recent activity