← previous blocknext block →recent activity
Analyzing
Block #103,221,141
13 transactions · 13 stateful · 2026-09-09 03:44:38 UTC
Parallelism
77/100
Blocked
23%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #103,221,141 · 13 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
1w02w18w09w111w012w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfdc57502…d80e
0x34b655…2a6f
4 touches
1 conflict
0xe53bd661…5352
0x34b655…2a6f
4 touches
1 conflict
0xeef0d7a2…ad6d
0x34b655…2a6f
4 touches
1 conflict
0x114a5de1…8b7f
0x34b655…2a6f
4 touches
1 conflict
0x1513b999…b52e
0x34b655…2a6f
4 touches
1 conflict
0x18e881c5…b740
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x455522d8…16f8
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 0xfdc5750274…b5d80e
Audit this contract →
← previous block·next block →recent activity