← previous blocknext block →recent activity
Analyzing
Block #106,033,618
29 transactions · 26 stateful · 2026-09-19 00:26:15 UTC
Parallelism
83/100
Blocked
46%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,033,618 · 29 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
1w02w03w14w05w16w27w08w111w012w113w015w119w123w324w126w227w328w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x48ed1159…abe9
0x34ae4d…3fc5
4 touches
1 conflict
0x03985714…c8ac
0x34b655…2a6f
4 touches
1 conflict
0x6435bd34…b160
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xd0caf939…ce30
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity