← previous blocknext block →recent activity
Analyzing
Block #99,187,113
17 transactions · 15 stateful · 2026-08-26 00:34:44 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,187,113 · 17 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
4w05w111w013w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd7443f37…eb79
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x54c8c0a4…812a
0x34b655…2a6f
4 touches
1 conflict
0x6d689901…15a1
0x065c9d…c394
2 touches
0 conflicts
0x7cf60fab…8e6b
0x065c9d…c394
2 touches
0 conflicts
0xf38d7639…e078
0x065c9d…c394
2 touches
0 conflicts
0x11258774…9892
0x2a68ba…90c5
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
1 conflict on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity