← previous blocknext block →recent activity
Analyzing
Block #102,401,043
13 transactions · 11 stateful · 2026-09-06 06:44:17 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,401,043 · 13 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
2w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfa5537c0…b528
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xb70e8194…17c9
0x34b655…2a6f
4 touches
1 conflict
0x24c5620c…7ac5
0x34b655…2a6f
2 touches
0 conflicts
0x3a90fb70…ce92
0x34b655…2a6f
2 touches
0 conflicts
0x3d2a5764…3d08
0x34b655…2a6f
2 touches
0 conflicts
0x5f72d58f…c445
0x34b655…2a6f
2 touches
0 conflicts
0x630b7b7a…3ece
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 0xfa5537c040…5bb528
Audit this contract →
← previous block·next block →recent activity