← previous blocknext block →recent activity
Analyzing
Block #107,823,536
19 transactions · 18 stateful · 2026-09-25 06:38:41 UTC
Parallelism
74/100
Blocked
44%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,823,536 · 19 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
2w03w18w09w110w211w012w213w314w415w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8753ff9…2a9f
0x34b655…2a6f
8 touches
6 conflicts
0xa2c4d203…05b6
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x3f451a59…e324
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xfa2794a8…40de
0x34b655…2a6f
4 touches
1 conflict
0x232b0b19…d946
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
6 conflicts on slot 0xa8753ff917…032a9f
Audit this contract →
← previous block·next block →recent activity