← previous blocknext block →recent activity
Analyzing
Block #106,017,613
17 transactions · 15 stateful · 2026-09-18 23:05:42 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,017,613 · 17 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
1w02w13w07w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x662e354e…e306
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x50b7cef1…a51a
0xee8c0e…1242
4 touches
1 conflict
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x729c91b8…9539
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0000
0x25ef1a…5bf1
2 touches
0 conflicts
0x00000000…0002
0x25ef1a…5bf1
2 touches
0 conflicts
0x00000000…0158
0x25ef1a…5bf1
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 0x662e354ec7…b7e306
Audit this contract →
← previous block·next block →recent activity