← previous blocknext block →recent activity
Analyzing
Block #107,795,816
16 transactions · 12 stateful · 2026-09-25 04:19:11 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #107,795,816 · 16 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
5w08w09w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0f6f4f2…dffa
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xa7ba83b5…d0a8
0x34b655…2a6f
4 touches
1 conflict
0x246974e7…932e
0x065c9d…c394
2 touches
0 conflicts
0x5082bb2c…3139
0x065c9d…c394
2 touches
0 conflicts
0x7f65a6dc…57dd
0x065c9d…c394
2 touches
0 conflicts
0xab6f49eb…c7af
0x065c9d…c394
2 touches
0 conflicts
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 0xd0f6f4f225…4cdffa
Audit this contract →
← previous block·next block →recent activity