← previous blocknext block →recent activity
Analyzing
Block #100,151,752
15 transactions · 14 stateful · 2026-08-29 09:44:29 UTC
Parallelism
73/100
Blocked
21%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,151,752 · 15 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
2w09w110w211w013w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3cbf2bf…04c0
0x34b655…2a6f
6 touches
3 conflicts
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0xd2a76d80…ee44
0x34b655…2a6f
4 touches
1 conflict
0xe9457301…83cd
0x34b655…2a6f
4 touches
1 conflict
0xedee7e09…6888
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x10379e8d…3675
0x34b655…2a6f
2 touches
0 conflicts
0x1d9867ad…6d9a
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
3 conflicts on slot 0xa3cbf2bf0e…1e04c0
Audit this contract →
← previous block·next block →recent activity