← previous blocknext block →recent activity
Analyzing
Block #102,173,816
21 transactions · 16 stateful · 2026-09-05 11:33:02 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #102,173,816 · 21 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
2w03w04w111w113w016w117w118w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7002df9e…1763
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xd5982776…4846
0x34b655…2a6f
4 touches
1 conflict
0xe6565037…c2bc
0x34b655…2a6f
4 touches
1 conflict
0x085df2c1…305a
0x34b655…2a6f
4 touches
1 conflict
0x36a2423d…e290
0x34b655…2a6f
4 touches
1 conflict
0x4d7aaa4f…a8ec
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 0x7002df9e9b…101763
Audit this contract →
← previous block·next block →recent activity