← previous blocknext block →recent activity
Analyzing
Block #100,984,050
13 transactions · 10 stateful · 2026-09-01 07:35:58 UTC
Parallelism
77/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,984,050 · 13 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
4w05w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x953517cb…cdec
0x34b655…2a6f
6 touches
3 conflicts
0x4a538b72…479c
0x34b655…2a6f
6 touches
3 conflicts
0x35006f8a…8e7f
0x34b655…2a6f
4 touches
1 conflict
0x4147b177…c9ba
0x34b655…2a6f
4 touches
1 conflict
0x9a100e05…c541
0x34b655…2a6f
4 touches
1 conflict
0xd2fd6de4…1729
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x48ed1159…abe9
0x34ae4d…3fc5
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
3 conflicts on slot 0x953517cb5b…8dcdec
Audit this contract →
← previous block·next block →recent activity