← previous blocknext block →recent activity
Analyzing
Block #106,035,336
14 transactions · 13 stateful · 2026-09-19 00:34:54 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,035,336 · 14 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
1w02w03w15w16w07w111w112w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x023277a7…72b5
0x34b655…2a6f
4 touches
1 conflict
0x11db128b…1153
0x34b655…2a6f
4 touches
1 conflict
0x1696ea61…6e38
0x34b655…2a6f
4 touches
1 conflict
0x17e078f4…c2b7
0x34b655…2a6f
4 touches
1 conflict
0x2a949bb2…8769
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x5dabd855…8ffb
0x34b655…2a6f
4 touches
1 conflict
0x70453369…1729
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 0x023277a719…ea72b5
Audit this contract →
← previous block·next block →recent activity