← previous blocknext block →recent activity
Analyzing
Block #101,665,998
17 transactions · 14 stateful · 2026-09-03 16:47:19 UTC
Parallelism
82/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #101,665,998 · 17 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
2w03w05w112w213w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6edb3e8…48be
0x34b655…2a6f
4 touches
1 conflict
0x230b0b56…a675
0x34b655…2a6f
4 touches
1 conflict
0x4089d428…b018
0x34b655…2a6f
4 touches
1 conflict
0x4c15b948…d02e
0x34b655…2a6f
4 touches
1 conflict
0x64abb586…81fe
0x34b655…2a6f
4 touches
1 conflict
0x77728311…ae0c
0x34b655…2a6f
4 touches
1 conflict
0x9b4f173c…94e6
0x34b655…2a6f
4 touches
1 conflict
0xa56162e1…a2e5
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 0xb6edb3e816…0748be
Audit this contract →
← previous block·next block →recent activity