← previous blocknext block →recent activity
Analyzing
Block #93,150,817
23 transactions · 22 stateful · 2026-08-04 20:02:00 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,150,817 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w28w09w110w211w312w415w320w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xaba62823…a926
0xe52b14…7230
9 touches
10 conflicts
0xbd557c8e…3dba
0x34b655…2a6f
6 touches
3 conflicts
0xb9834665…e363
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x5d6e4470…4b4c
0x34b655…2a6f
4 touches
1 conflict
0x5d7e0e69…e6d1
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: 0xe52b1424…bb7230
10 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity