← previous blocknext block →recent activity
Analyzing
Block #105,626,401
20 transactions · 16 stateful · 2026-09-17 14:14:15 UTC
Parallelism
90/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #105,626,401 · 20 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
7w08w114w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x126c10ea…a328
0x34b655…2a6f
4 touches
1 conflict
0x199a4f01…2183
0x34b655…2a6f
4 touches
1 conflict
0x1eb0fab5…3517
0x34b655…2a6f
4 touches
1 conflict
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x3bb680b4…09ef
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
4 touches
1 conflict
0x6f95cc9f…e9b5
0x34b655…2a6f
4 touches
1 conflict
0x7f127ad0…2bd6
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 0x126c10eae3…91a328
Audit this contract →
← previous block·next block →recent activity