← previous blocknext block →recent activity
Analyzing
Block #106,215,487
23 transactions · 21 stateful · 2026-09-19 15:41:34 UTC
Parallelism
87/100
Blocked
38%
Avg conflicts / tx
0.61
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,215,487 · 23 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
2w03w16w07w08w09w210w011w113w115w220w121w222w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x962baf1c…c923
0x34b655…2a6f
6 touches
3 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa605468c…1bfc
0x34ae4d…3fc5
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x1a1da822…8d50
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
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 0x962baf1c95…98c923
Audit this contract →
← previous block·next block →recent activity