← previous blocknext block →recent activity
Analyzing
Block #94,952,289
18 transactions · 17 stateful · 2026-08-11 03:19:01 UTC
Parallelism
89/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,952,289 · 18 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
4w05w16w010w011w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef1cbbb7…8cc8
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x2b5101ac…090b
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x5e17e5be…d212
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x7f4a8466…f2cc
0x2b46c0…1669
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 0xef1cbbb7ac…328cc8
Audit this contract →
← previous block·next block →recent activity