← previous blocknext block →recent activity
Analyzing
Block #94,483,603
22 transactions · 22 stateful · 2026-08-09 12:00:08 UTC
Parallelism
77/100
Blocked
41%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,483,603 · 22 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
1w02w05w06w17w18w29w311w012w113w214w316w417w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xd44e517e…8d2f
0x34b655…2a6f
8 touches
6 conflicts
0x2b145e60…dc48
0x065c9d…c394
6 touches
3 conflicts
0x0778475b…bd75
0x2a68ba…90c5
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x61d37f4f…61d2
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
10 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity