← previous blocknext block →recent activity
Analyzing
Block #93,844,239
13 transactions · 11 stateful · 2026-08-07 06:08:08 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,844,239 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe196f841…22e3
0x34b655…2a6f
4 touches
1 conflict
0xe196f841…22e4
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0x2550f1c1…a0e4
0x34b655…2a6f
4 touches
1 conflict
0x3559b524…7226
0x34b655…2a6f
4 touches
1 conflict
0x3fead0ae…0e35
0x34b655…2a6f
4 touches
1 conflict
0x53ca1284…cb2c
0x34b655…2a6f
4 touches
1 conflict
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 0xe196f8419b…9322e3
Audit this contract →
← previous block·next block →recent activity