← previous blocknext block →recent activity
Analyzing
Block #102,843,908
22 transactions · 20 stateful · 2026-09-07 20:04:05 UTC
Parallelism
91/100
Blocked
20%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #102,843,908 · 22 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
1w02w06w08w010w114w116w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49d6800f…40eb
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x1450e2d4…4d37
0x34b655…2a6f
2 touches
0 conflicts
0x19040261…3586
0x34b655…2a6f
2 touches
0 conflicts
0x1f459632…a5d9
0x34b655…2a6f
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 0x49d6800ff5…3a40eb
Audit this contract →
← previous block·next block →recent activity