← previous blocknext block →recent activity
Analyzing
Block #92,547,801
17 transactions · 16 stateful · 2026-08-02 17:25:58 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,547,801 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w18w211w312w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa494952f…d178
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x427d1120…4eb1
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
4 touches
1 conflict
0x8faba3a7…8454
0x34b655…2a6f
4 touches
1 conflict
0xa03c2a35…52e6
0x34b655…2a6f
4 touches
1 conflict
0x4b9553ce…3126
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
6 conflicts on slot 0xa494952f82…55d178
Audit this contract →
← previous block·next block →recent activity