← previous blocknext block →recent activity
Analyzing
Block #108,681,640
36 transactions · 31 stateful · 2026-09-28 06:38:01 UTC
Parallelism
92/100
Blocked
26%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,681,640 · 36 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w17w08w110w011w114w016w119w221w022w133w134w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1c4d8e8…ffa8
0x508254…98bd
4 touches
1 conflict
0x443a3e47…f4a4
0x065c9d…c394
4 touches
1 conflict
0xaf448337…cb60
0x508254…98bd
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0xb75367ff…a2b7
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: 0x508254c8…4a98bd
1 conflict on slot 0xe1c4d8e8bd…deffa8
Audit this contract →
← previous block·next block →recent activity