← previous blocknext block →recent activity
Analyzing
Block #93,267,832
19 transactions · 17 stateful · 2026-08-05 05:50:19 UTC
Parallelism
89/100
Blocked
6%
Avg conflicts / tx
0.16
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,267,832 · 19 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
2w011w016w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x84d74093…7808
0x34b655…2a6f
4 touches
1 conflict
0xc4dd535c…2529
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdfc21d7c…e062
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x9e98214a…9927
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
0x34b655…2a6f
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 0x5eb187dd4c…a6b1d6
Audit this contract →
← previous block·next block →recent activity