← previous blocknext block →recent activity
Analyzing
Block #100,747,871
17 transactions · 11 stateful · 2026-08-31 11:47:31 UTC
Parallelism
82/100
Blocked
27%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,747,871 · 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
4w05w16w213w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1d351a9b…f2dd
0x34b655…2a6f
6 touches
3 conflicts
0x81716ce9…095f
0x34b655…2a6f
4 touches
1 conflict
0x728dd961…8676
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcd3eda74…bc79
0x34b655…2a6f
4 touches
1 conflict
0xe720a4c6…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0029
0x1b6862…e19c
2 touches
0 conflicts
0xd5b10148…e632
0x1b6862…e19c
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 0x1d351a9b20…2df2dd
Audit this contract →
← previous block·next block →recent activity