← previous blocknext block →recent activity
Analyzing
Block #100,143,554
12 transactions · 9 stateful · 2026-08-29 09:03:14 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #100,143,554 · 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
3w08w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5080be1…5794
0x8964d7…10f8
4 touches
1 conflict
0x3d8f4ec3…12b6
0x8964d7…10f8
4 touches
1 conflict
0x3d8f4ec3…12b7
0x8964d7…10f8
4 touches
1 conflict
0x3d8f4ec3…12ba
0x8964d7…10f8
4 touches
1 conflict
0x3d8f4ec3…12bb
0x8964d7…10f8
4 touches
1 conflict
0x3d8f4ec3…12bd
0x8964d7…10f8
4 touches
1 conflict
0xc5080be1…5791
0x8964d7…10f8
4 touches
1 conflict
0xc5080be1…5792
0x8964d7…10f8
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 0xc5080be10a…0d5794
Audit this contract →
← previous block·next block →recent activity