← previous blocknext block →recent activity
Analyzing
Block #103,210,731
15 transactions · 15 stateful · 2026-09-09 02:52:11 UTC
Parallelism
87/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #103,210,731 · 15 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
2w03w16w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x064f7e21…18ec
0x34b655…2a6f
4 touches
1 conflict
0x0f763490…ff64
0x34b655…2a6f
4 touches
1 conflict
0x18cf84a6…09e4
0x34b655…2a6f
4 touches
1 conflict
0x22b4a41c…e29f
0x34b655…2a6f
4 touches
1 conflict
0x2f17174f…68b4
0x34b655…2a6f
4 touches
1 conflict
0x3027f5b0…7a3f
0x34b655…2a6f
4 touches
1 conflict
0x36aa792c…a68d
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
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 0x064f7e217f…ca18ec
Audit this contract →
← previous block·next block →recent activity