← previous blocknext block →recent activity
Analyzing
Block #101,797,963
19 transactions · 18 stateful · 2026-09-04 03:51:05 UTC
Parallelism
89/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,797,963 · 19 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
3w09w010w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa60eabc0…9f8c
0x34b655…2a6f
4 touches
1 conflict
0xdb554de7…89fa
0x34b655…2a6f
4 touches
1 conflict
0x4ee0b65a…6d40
0x34b655…2a6f
4 touches
1 conflict
0x97c67486…27fe
0x34b655…2a6f
4 touches
1 conflict
0x09aff580…d5a1
0x34b655…2a6f
2 touches
0 conflicts
0x146a9750…f938
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x2d94ecd9…43db
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 0xa60eabc0f8…119f8c
Audit this contract →
← previous block·next block →recent activity