← previous blocknext block →recent activity
Analyzing
Block #101,680,001
13 transactions · 12 stateful · 2026-09-03 17:57:46 UTC
Parallelism
85/100
Blocked
25%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #101,680,001 · 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
1w02w03w16w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2e05467a…e3b3
0x34b655…2a6f
4 touches
1 conflict
0x041d6cf6…e9d7
0x34b655…2a6f
4 touches
1 conflict
0x9e0f1bec…86e0
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xdbb571e4…6829
0x34b655…2a6f
4 touches
1 conflict
0xf339fa40…54c2
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x2aa7be4c…0f84
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 0x2e05467aa3…15e3b3
Audit this contract →
← previous block·next block →recent activity