← previous blocknext block →recent activity
Analyzing
Block #108,873,960
85 transactions · 81 stateful · 2026-09-28 22:49:02 UTC
Parallelism
98/100
Blocked
5%
Avg conflicts / tx
0.05
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,873,960 · 85 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
1w03w17w08w112w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ad5e6de…e7ad
0x34b655…2a6f
4 touches
1 conflict
0x5fa6e1a0…c881
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x4c29ecd5…58b6
0x34b655…2a6f
4 touches
1 conflict
0xbd3735d7…c973
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x945d1dbe…e1d7
0xc8689a…ee79
4 touches
1 conflict
0xf4a97154…2d71
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: Perpl
1 conflict on slot 0x5ad5e6deb1…38e7ad
Audit this contract →
← previous block·next block →recent activity