← previous blocknext block →recent activity
Analyzing
Block #101,922,224
31 transactions · 23 stateful · 2026-09-04 14:17:21 UTC
Parallelism
87/100
Blocked
43%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,922,224 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w07w18w09w010w116w017w124w126w327w129w230w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe53bd661…5352
0x34b655…2a6f
6 touches
3 conflicts
0xe8f860c0…35c9
0x34b655…2a6f
6 touches
3 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
6 touches
3 conflicts
0xb826ef15…d248
0x34b655…2a6f
6 touches
3 conflicts
0xda09bbc9…b41b
0x34b655…2a6f
6 touches
3 conflicts
0x7c216fca…20cb
0x34b655…2a6f
4 touches
1 conflict
0x8bf6e6e7…be00
0x34b655…2a6f
4 touches
1 conflict
0x999c658d…b185
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
3 conflicts on slot 0xe53bd661fb…e85352
Audit this contract →
← previous block·next block →recent activity