← previous blocknext block →recent activity
Analyzing
Block #98,483,181
14 transactions · 13 stateful · 2026-08-23 12:50:17 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,483,181 · 14 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
3w04w17w08w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b7e8e52…6e30
0x34b655…2a6f
4 touches
1 conflict
0x8c49c85c…ee96
0x34b655…2a6f
4 touches
1 conflict
0xd0f6f4f2…dffa
0x34b655…2a6f
4 touches
1 conflict
0xd459bf7b…92c3
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x3129b531…9db1
0x754704…b603
2 touches
0 conflicts
0x64b004ab…60af
0x754704…b603
2 touches
0 conflicts
0xba68e65e…c29a
0x754704…b603
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 0x5b7e8e5245…ad6e30
Audit this contract →
← previous block·next block →recent activity