← previous blocknext block →recent activity
Analyzing
Block #93,452,136
12 transactions · 11 stateful · 2026-08-05 21:16:58 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,452,136 · 12 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
1w02w13w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xabf57eb6…416d
0x34b655…2a6f
4 touches
1 conflict
0xc46dfd53…3305
0x34b655…2a6f
4 touches
1 conflict
0x1af53e83…c72e
0x754704…b603
4 touches
1 conflict
0x37e1e6f1…84d0
0x754704…b603
4 touches
1 conflict
0x7e8cd4a2…8fc0
0x754704…b603
4 touches
1 conflict
0x13ec4c5f…a778
0x99c7a7…8bf0
4 touches
1 conflict
0xd930d57a…3bfb
0x99c7a7…8bf0
4 touches
1 conflict
0x25bd9829…29bf
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 0xabf57eb66c…0a416d
Audit this contract →
← previous block·next block →recent activity