← previous blocknext block →recent activity
Analyzing
Block #100,982,963
17 transactions · 16 stateful · 2026-09-01 07:30:30 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,982,963 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc63ade7…8260
0x34b655…2a6f
4 touches
1 conflict
0x974cf1b9…1e1d
0x34b655…2a6f
4 touches
1 conflict
0xa073fab5…8c0d
0x34b655…2a6f
4 touches
1 conflict
0xaaf36ccb…f35c
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xda50c9d5…674e
0x34b655…2a6f
4 touches
1 conflict
0xec3e277e…3dba
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 0xfc63ade734…1e8260
Audit this contract →
← previous block·next block →recent activity