← previous blocknext block →recent activity
Analyzing
Block #93,356,864
17 transactions · 17 stateful · 2026-08-05 13:17:58 UTC
Parallelism
65/100
Blocked
41%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,356,864 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w16w27w010w311w412w213w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x138ed846…08c9
0x34b655…2a6f
12 touches
15 conflicts
0x45ea7a97…bbb3
0x34b655…2a6f
6 touches
3 conflicts
0x4aaa2679…4c1d
0x34b655…2a6f
4 touches
1 conflict
0x4af8f8d2…0850
0x34b655…2a6f
4 touches
1 conflict
0x8faba3a7…8454
0x34b655…2a6f
4 touches
1 conflict
0xa6311649…0132
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
15 conflicts on slot 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity