← previous blocknext block →recent activity
Analyzing
Block #101,501,368
18 transactions · 16 stateful · 2026-09-03 02:59:08 UTC
Parallelism
83/100
Blocked
19%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,501,368 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69d2053b…935a
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0xbc8fb280…76a3
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe1c4e5ce…0dec
0x34b655…2a6f
4 touches
1 conflict
0x1b073461…682f
0x34b655…2a6f
2 touches
0 conflicts
0x336486a4…20bd
0x34b655…2a6f
2 touches
0 conflicts
0x387f5670…d098
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 0x69d2053b7f…ea935a
Audit this contract →
← previous block·next block →recent activity