← previous blocknext block →recent activity
Analyzing
Block #101,970,236
12 transactions · 12 stateful · 2026-09-04 18:20:57 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,970,236 · 12 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
1w02w14w05w17w08w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0x06a8b17c…46e5
0x754704…b603
4 touches
1 conflict
0x420c4a20…aa5f
0x754704…b603
4 touches
1 conflict
0x7805c8f7…1376
0x754704…b603
4 touches
1 conflict
0x461e2f32…8325
0x99c7a7…8bf0
4 touches
1 conflict
0x6c02fb45…7ae9
0x99c7a7…8bf0
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0xd29e547b5d…35a1dd
Audit this contract →
← previous block·next block →recent activity