← previous blocknext block →recent activity
Analyzing
Block #93,227,294
18 transactions · 17 stateful · 2026-08-05 02:26:31 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.44
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,227,294 · 18 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
2w03w06w18w09w113w215w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fab7fbe…1ce5
0x34b655…2a6f
6 touches
3 conflicts
0x48965dfe…432b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x124a2fe8…2ea9
0x34b655…2a6f
6 touches
3 conflicts
0x19840da5…08b8
0x34b655…2a6f
4 touches
1 conflict
0x1c2c1569…24b0
0x34b655…2a6f
4 touches
1 conflict
0x1e9cb946…7951
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
3 conflicts on slot 0x5fab7fbe22…391ce5
Audit this contract →
← previous block·next block →recent activity