← previous blocknext block →recent activity
Analyzing
Block #100,143,080
12 transactions · 12 stateful · 2026-08-29 09:00:50 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,143,080 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x85026d38…0799
0x8964d7…10f8
4 touches
1 conflict
0x16269ba2…a1e4
0x8964d7…10f8
4 touches
1 conflict
0x16269ba2…a1e7
0x8964d7…10f8
4 touches
1 conflict
0x16269ba2…a1e8
0x8964d7…10f8
4 touches
1 conflict
0x16269ba2…a1ea
0x8964d7…10f8
4 touches
1 conflict
0x85026d38…0796
0x8964d7…10f8
4 touches
1 conflict
0x85026d38…0797
0x8964d7…10f8
4 touches
1 conflict
0x261cbea7…e35d
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: 0x8964d7c9…5b10f8
1 conflict on slot 0x85026d38b4…4b0799
Audit this contract →
← previous block·next block →recent activity