← previous blocknext block →recent activity
Analyzing
Block #101,150,783
23 transactions · 14 stateful · 2026-09-01 21:35:10 UTC
Parallelism
91/100
Blocked
29%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,150,783 · 23 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
4w06w110w011w116w017w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6de33f7d…1862
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe22455da…1ce1
0x34b655…2a6f
4 touches
1 conflict
0xf1894e7f…30fe
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x5906754f…b584
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
1 conflict on slot 0x6de33f7d0d…c61862
Audit this contract →
← previous block·next block →recent activity