← previous blocknext block →recent activity
Analyzing
Block #106,242,820
19 transactions · 17 stateful · 2026-09-19 17:59:11 UTC
Parallelism
89/100
Blocked
24%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,242,820 · 19 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
1w02w16w010w114w015w116w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65e57979…e43d
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x4d2e71c2…da75
0x34b655…2a6f
2 touches
0 conflicts
0x708d7a74…09e3
0x34b655…2a6f
2 touches
0 conflicts
0xe9665c47…f2d9
0x34b655…2a6f
2 touches
0 conflicts
0xec7d120d…7084
0x34b655…2a6f
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 0x65e579798d…35e43d
Audit this contract →
← previous block·next block →recent activity