← previous blocknext block →recent activity
Analyzing
Block #108,010,029
19 transactions · 18 stateful · 2026-09-25 22:17:25 UTC
Parallelism
79/100
Blocked
28%
Avg conflicts / tx
0.32
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,010,029 · 19 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w08w112w213w015w118w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ae436cb…7d34
0x34b655…2a6f
4 touches
1 conflict
0xc2374606…93f7
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xf5dc501b…831c
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
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 0x9ae436cb2c…c57d34
Audit this contract →
← previous block·next block →recent activity