← previous blocknext block →recent activity
Analyzing
Block #100,983,954
22 transactions · 17 stateful · 2026-09-01 07:35:29 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,983,954 · 22 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
1w03w04w17w08w19w216w017w318w119w120w021w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2fd6de4…1729
0x34b655…2a6f
8 touches
6 conflicts
0x953517cb…cdec
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x85bfd0af…ce96
0x34b655…2a6f
6 touches
3 conflicts
0xdceeb8ff…0937
0x34b655…2a6f
6 touches
3 conflicts
0x9a100e05…c541
0x34b655…2a6f
6 touches
3 conflicts
0x35006f8a…8e7f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
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
6 conflicts on slot 0xd2fd6de4a1…5c1729
Audit this contract →
← previous block·next block →recent activity