← previous blocknext block →recent activity
Analyzing
Block #107,841,752
17 transactions · 15 stateful · 2026-09-25 08:10:22 UTC
Parallelism
71/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,841,752 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w08w110w211w312w414w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0xfd92a40c…d9e0
0x34b655…2a6f
4 touches
1 conflict
0x3ff9db2e…22f6
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x438b9fc3…386b
0x34b655…2a6f
4 touches
1 conflict
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0xc3771f33…3f33
0x34b655…2a6f
4 touches
1 conflict
0xc7679110…572d
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity